jiebi/CodeConvo huggingface dataset:
Change:
There is a display bug in section of and values are not displayed properly as is. ! I guess the list of values should be looking like this: Exact: Matches the URL path exactly. Prefix: Matches based on a URL path prefix split by '/'. Matching is done on a path element by element basis. A path element refers is the list of labels in the path split by the '/' separator. A request is a match for path p if every p is an element-wise prefix of p of the request path. Note that if the last element of the path is a substring of the last element in request path, it is not a match (e.g. /foo/bar matches /foo/bar/baz, but does not match /foo/barbaz). ImplementationSpecific: Interpretation of the Path matching is up to the IngressClass. Implementations can treat this as a separate PathType or treat it identically to Prefix or Exact path types. Implementations are required to support all path types.
/retitle Display bug in section of Ingress API referenc /sig docs /language en /triage accepted /priority backlog This could be seen as a feature request for the that generates API reference docs.
/retitle Display bug in section of Ingress API reference
/retitle Display bug in section of Ingress API referenc
/assign

Discussion:
- **rules.http.paths.pathType** (string), required <del> PathType determines the interpretation of the Path matching. PathType can be one of the following values: * Exact: Matches the URL path exactly. * Prefix: Matches based on a URL path prefix split by '/'. Matching is </del> <ins> PathType determines the interpretation of the Path matching. PathType can be one of the following values: * Exact: Matches the URL path exactly. * Prefix: Matches based on a URL path prefix split by '/'. Matching is </ins> done on a path element by element basis. A path element refers is the list of labels in the path split by the '/' separator. A request is a match for path p if every p is an element-wise prefix of p of the request path. Note that if the last element of the path is a substring of the last element in request path, it is not a match (e.g. /foo/bar matches /foo/bar/baz, but does not match /foo/barbaz). * ImplementationSpecific: Interpretation of the Path matching is up to the IngressClass. Implementations can treat this as a separate PathType or treat it identically to Prefix or Exact path types.
Change:
Problem: The text on should point to these Check the page for the problem. Page to Update: Proposed Solution: It should resolve this issue by adding a simple link and enhancing the document line. Update the link on the text example to and not to this . /kind document /assign /language en
The label(s) cannot be applied, because the repository doesn't have them. <detailsIn response to : Problem: The text on should point to these Check the page for the problem. It should resolve this issue by adding a simple link and enhancing the document line. Update the link on the text example to and not to this . /assign /language en Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details
/triage accepted

Discussion:
each of them. Unlabeled namespaces should only indicate that they've yet to be evaluated. In the scenario that all workloads in all namespaces have the same security requirements, <del> we provide an [example](/docs/concepts/security/pod-security-admission/#applying-to-all-namespaces) </del> <ins> we provide an [example](/docs/tasks/configure-pod-container/enforce-standards-namespace-labels/#applying-to-all-namespaces) </ins> that illustrates how the PodSecurity labels can be applied in bulk. ### Embrace the principle of least privilege
Change:
This is a Bug Report <!-- Thanks for filing an issue! Before submitting, please fill in the following information. --<!-- See for guidance on writing an actionable issue description. --<!--Required Information--Problem: ! Proposed Solution: when run make container-serve on windows 10 then got :loading translations: "": failed to load translations: toml: invalid character at start of key: . Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--
Maybe-relevant issue:
first delete the i18n dir then run mklink /J "E:sourcecodek8s-websitei18n" "E:sourcecodek8s-websitedatai18n"
This is a Windows issue (and is almost a duplicate of ) /retitle Trouble previewing website locally on Windows
/triage accepted
The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs. This bot triages issues and PRs according to the following rules: After 90d of inactivity, is applied After 30d of inactivity since was applied, is applied After 30d of inactivity since was applied, the issue is closed You can: Mark this issue or PR as fresh with Mark this issue or PR as rotten with Close this issue or PR with Offer to help out with [Issue Triage][1] Please send feedback to sig-contributor-experience at . /lifecycle stale [1]:
I want to work on this issue. /assign
/remove-lifecycle stale

Discussion:
# Weight used for sorting. weight = 1 languagedirection = "ltr" <ins> i18nDir = "./data/i18n" </ins> [languages.zh-cn] title = "Kubernetes"

[languages.uk.params] time_format_blog = "02.01.2006" # A list of language codes to look for untranslated content, ordered from left to right. <del> language_alternatives = ["en"] </del> <ins> language_alternatives = ["en"] </ins>  No newline at end of file
Change:
This is a Feature Request "Host Ports" rule have the following description "HostPorts should be disallowed, or at minimum restricted to a known list." It is not clear for the reader that this statement is composed from two mutually exclusive terms "HostPorts should be disallowed” OR “HostPorts should be restricted to a known list." Additionally, it is not clear that Pod Security Admission Controller implements the first option and the second one is for 3rd party controllers like Gatekeeper/Kyverno. What would you like to be "Host Ports" rule can be rephrased so it is clear that it consist of two mutually exclusive options. Or it be divided into two separate rules (two rows in the table). doc or/and doc should clearly state which "Host Ports" option is implemented by the "Pod Security Admission" Why is this needed Pod Security Standards doc can mislead user. Comments
/language en /sig security
/sig auth
/remove-kind feature /kind bug
If we're updating the PSA doc, we should perhaps work with sig-auth ( maybe) to identify if there are other Pod Security Standards where PSA only enforces a specific condition or behaviour by default.
Yes, I agree. I'd be OK with just change this to "HostPorts should be disallowed". The standards used to include more optional restrictions, but we've been making them more opinionated (and aligned with the PSA implementation) over time.
/triage accepted
/assign
I don't see any updates; so unassigning you. Please feel free to assign, if you come back here again and are willing to work on /unassign
For the adventurous contributor looking for a good issue, here's what you need to do: In the Host Ports row in , replace the first sentence with "HostPorts should be disallowed." For instructions to edit a page and create a PR, use in our contributor guide /help-wanted

Discussion:
<tr> <td style="white-space: nowrap">Host Ports</td> <td> <del> <p>HostPorts should be disallowed, or at minimum restricted to a known list.</p> </del> <ins> <p>HostPorts should be disallowed entirely (recommended) or restricted to a known list</p> </ins> <p><strong>Restricted Fields</strong></p> <ul> <li><code>spec.containers[*].ports[*].hostPort</code></li>

<p><strong>Allowed Values</strong></p> <ul> <li>Undefined/nil</li> <del> <li>Known list</li> </del> <ins> <li>Known list (not supported by the built-in <a href="/docs/concepts/security/pod-security-admission/">Pod Security Admission controller</a>)</li> </ins> <li><code>0</code></li> </ul> </td>
Change:
<html <!--StartFragment----service-account-issuer strings | "iss" URI OpenID Discovery 1.0 URI true ServiceAccountIssuerDiscovery OpenID service-account-issuer HTTPS URL URL {service-account-issuer}/.well-known/openid-configuration OpenID <!--EndFragment--“” </body</html
/language zh I assume this is a bug report. If possible, clarify whether the issue is with the upstream (English) docs or with the way those docs have been localized. /triage needs-information
The label(s) cannot be applied, because the repository doesn't have them. <detailsIn response to : /triage bug Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details
/kind bug /triage accepted
/assign

Discussion:
and all are used to determine which issuers are accepted. --> 服务帐号令牌颁发者的标识符。 <del> 颁发者将在已办法令牌的 "iss" 声明中检查此标识符。 </del> <ins> 颁发者将在已颁发令牌的 "iss" 声明中检查此标识符。 </ins> 此值为字符串或 URI。 如果根据 OpenID Discovery 1.0 规范检查此选项不是有效的 URI，则即使特性门控设置为 true， ServiceAccountIssuerDiscovery 功能也将保持禁用状态。
Change:
The alternative mentioned on this page is identical to the thing it is supposed to replace: This first example used to use to recursively return all fields named image for all items returned, but now it uses the same jsonpath as the alternative below it: Suggest removing the following text: See:
This issue is currently awaiting triage. SIG Docs takes a lead on issue triage for this website, but any Kubernetes member can accept issues by applying the label. The label can be by org members by writing in a comment. <detailsInstructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details
/language en
/assign

Discussion:
sort | uniq -c ``` <del> The above command will recursively return all fields named `image` for all items returned. As an alternative, it is possible to use the absolute path to the image field within the Pod.  This ensures the correct field is retrieved even when the field name is repeated, e.g. many fields are called `name` within a given item: ```shell kubectl get pods --all-namespaces -o jsonpath="{.items[*].spec.containers[*].image}" ``` </del> The jsonpath is interpreted as follows: - `.items[*]`: for each returned value
Change:
This is a Feature Request <!-- Please only use this template for submitting feature/enhancement requests --<!-- See for guidance on writing an actionable issue description. --What would you like to be Add a comment to the example Kubernetes client config in Why is this needed Storing a password in a Kubernetes client config is risky, and we have an opportunities to call out other options. Comments A good alternative is a and separate secret storage. /language en /sig security
once this issue is triaged, I'd expect that contributors look at the issue and decide whether they know how to resolve it. If you - or anyone else - aren't sure how to resolve a particular issue, that's OK. In that case, you have a few options: ask in Kubernetes Slack for advice for this issue specifically, WG API Expression or SIG Security might be able to offer advice around good practice with password storage look on the web using a web search engine. For example, has links to pages that might offer advice here look for a different issue to work on. With over 200 other English language issues open, you may find another issue that you do know how to work on. It's OK not to work on an issue that you don't understand how to fix. In general, asking the person who reported the issue isn't the best way to get help. Sometimes they may know exactly what is wrong but not have a clear idea about what to do to fix it.
If you decide that you don't know how to work on this then I recommend that you unassign yourself, so it's clear to other contributors that help is needed here.
/triage accepted

Discussion:
Add user details to your configuration file: <ins> {{< caution >}} Storing passwords in Kubernetes client config is risky. A better alternative would be to use a credential plugin and store them separately. See: [client-go credential plugins](/docs/reference/access-authn-authz/authentication/#client-go-credential-plugins) {{< /caution >}} </ins> ```shell kubectl config --kubeconfig=config-demo set-credentials developer --client-certificate=fake-cert-file --client-key=fake-key-seefile kubectl config --kubeconfig=config-demo set-credentials experimenter --username=exp --password=some-password

client-key: fake-key-file - name: experimenter user: <ins> # Documentation note (this comment is NOT part of the command output). # Storing passwords in Kubernetes client config is risky. # A better alternative would be to use a credential plugin # and store the credentials separately. # See https://kubernetes.io/docs/reference/access-authn-authz/authentication/#client-go-credential-plugins </ins> password: some-password username: exp ```
Change:
Problem: The text opportunites is mistyped on the announcement section of . For the problem, check the page . File to Update: /good-first-issue /kind document /assign /language en
The label(s) cannot be applied, because the repository doesn't have them. <detailsIn response to : Problem: The text opportunites is mistyped on the announcement section of . For the problem, check the page . /kind document /assign /language en Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details
/remove-good-first-issue Banner changes are actually a bit weird.
/language en
/triage accepted

Discussion:
It conflicts with the [core values of the Kubernetes project](https://git.k8s.io/community/values.md) and our community does not tolerate it. - name: Kubecon 2021 EU <del> startTime: 2021-04-30T00:00:00 endTime: 2021-05-07T00:00:00 </del> <ins> startTime: 2021-04-30T00:00:00 endTime: 2021-05-07T00:00:00 </ins> style: "background-image: linear-gradient(90deg, rgb(249, 145, 6) 0%, rgb(252, 29, 68) 100%)" title: | <img src="/images/announcements/kubecon-eu-2021-white.svg" style="float: right; height: 80px;" />

<img src="/images/announcements/kubecon-NA-2021-white.svg" style="float: right; height: 80px;" /> <a href="https://events.linuxfoundation.org/kubecon-cloudnativecon-north-america/"> KubeCon + CloudNativeCon North America 2021</a> <em>Los Angeles, California + Virtual</em>. message: | <del> 5 days of incredible opportunites to collaborate, learn + share with the entire community!<br /> </del> <ins> 5 days of incredible opportunities to collaborate, learn + share with the entire community!<br /> </ins> October 11 - 15, 2021. - name: Kubecon 2021 China

<img src ="/images/announcements/kccnc-eu-2022-black.svg" style="float: right; height: 80px;" /> <a href= "https://events.linuxfoundation.org/kubecon-cloudnativecon-europe/">KubeCon + CloudNativeCon EU 2022</a> <em> Valencia, Spain + Virtual</em>. message: | <del> 5 days of incredible opportunites to collaborate, learn + share with the entire community!<br /> </del> <ins> 5 days of incredible opportunities to collaborate, learn + share with the entire community!<br /> </ins> May 16 - 20, 2022. - name: Kubecon 2022 NA

<img src="/images/announcements/kccnc-na-2022-white.svg" style="float: right; height: 80px;" /> <a href="https://events.linuxfoundation.org/kubecon-cloudnativecon-north-america/">KubeCon + CloudNativeCon NA 2022</a> <em>Detroit, Michigan + Virtual</em>. message: | <del> 5 days of incredible opportunites to collaborate, learn + share with the entire community!<br /> </del> <ins> 5 days of incredible opportunities to collaborate, learn + share with the entire community!<br /> </ins> October 24 - 28, 2022.
Change:
What would you like to be The spelling of the receiver i.e is wrong Why is this needed Fix Spelling Comments /language en /assign
/retitle Spelling mistake in Traces For Kubernetes System Components page
oh its already underway, don't mind me.
Hi can I work on this ?
/assign
actually, there already exists an open PR () that opened. /assign
Ok, Should I unassign myself ?
/unassign
/triage accepted
/kind bug /sig docs

Discussion:
trace spans. As with the apiserver, the endpoint and sampling rate are configurable. Trace context propagation is also configured. A parent span's sampling decision is always respected. A provided tracing configuration sampling rate will apply to spans without a parent. <del> Enabled without a configured endpoint, the default OpenTelemetry Collector reciever address of "localhost:4317" is set. </del> <ins> Enabled without a configured endpoint, the default OpenTelemetry Collector receiver address of "localhost:4317" is set. </ins> #### Enabling tracing in the kubelet
Change:
This is a Feature Request What would you like to be We need to update according to the English text, because it is outdated. Why is this needed "Questions", "Stack Overflow" and "Bugs and feature requests" sections are outdated. Questions: Change the URL /docs/reference/kubectl/overview/ to /docs/reference/kubectl/ for . Stack Overflow: Update the statement for how to ask a new question. Bugs and feature requests: Change "Docker version" to "container runtime version". Comments /language ja
/triage accepted
/assign

Discussion:
[コンセプト](/ja/docs/concepts/)では、Kubernetesのアーキテクチャと各コンポーネントの動作について説明し、[セットアップ](/ja/docs/setup/)では、使い始めるための実用的な手順を提供しています。 [タスク](/ja/docs/tasks/) は、よく使われるタスクの実行方法を示し、 [チュートリアル](/ja/docs/tutorials/)は、実世界の業界特有、またはエンドツーエンドの開発シナリオ、より包括的なウォークスルーとなります。 <del> [リファレンス](/ja/docs/reference/)セクションでは、[Kubernetes API](/docs/reference/generated/kubernetes-api/{{< param "version" >}}/)や[`kubectl`](/docs/reference/kubectl/overview/)などのコマンドラインインターフェース(CLI)に関する詳しいドキュメントが提供されています。 </del> <ins> [リファレンス](/ja/docs/reference/)セクションでは、[Kubernetes API](/docs/reference/generated/kubernetes-api/{{< param "version" >}}/)や[`kubectl`](/docs/reference/kubectl/)などのコマンドラインインターフェース(CLI)に関する詳しいドキュメントが提供されています。 </ins> ## ヘルプ!私の質問はカバーされていません!今すぐ助けてください!

コミュニティの誰かがすでに同じような質問をしている可能性があり、あなたの問題を解決できるかもしれません。 Kubernetesチームも[Kubernetesタグが付けられた投稿](https://stackoverflow.com/questions/tagged/kubernetes)を監視しています。 <del> もし役立つ既存の質問がない場合は、[新しく質問してみてください](https://stackoverflow.com/questions/ask?tags=kubernetes)。 </del> <ins> もし役立つ既存の質問がない場合は、[新しく質問する](https://stackoverflow.com/questions/ask?tags=kubernetes)前に、**[あなたの質問がStack Overflowのトピックに沿ったものであることを確認し](https://stackoverflow.com/help/on-topic)、[新しく質問する方法](https://stackoverflow.com/help/how-to-ask)のガイダンスに目を通してください！** </ins> ### Slack Kubernetesコミュニティの多くの人々は、Kubernetes Slackの`#kubernetes-users`チャンネルに集まっています。 <del> Slackは登録が必要です。[招待をリクエストする](https://slack.kubernetes.io)ことができ、登録は誰でも可能です）。 </del> <ins> Slackは登録が必要です。[招待をリクエストする](https://slack.kubernetes.io)ことができ、登録は誰でも可能です。 </ins> お気軽にお越しいただき、何でも質問してください。 登録が完了したら、WebブラウザまたはSlackの専用アプリから[Kubernetes organization in Slack](https://kubernetes.slack.com)にアクセスします。

バグを報告する場合は、そのバグを再現するための詳細な情報を含めてください。 * Kubernetes のバージョン: `kubectl version` <del> * クラウドプロバイダー、OSディストリビューション、ネットワーク構成、Dockerバージョン </del> <ins> * クラウドプロバイダー、OSディストリビューション、ネットワーク構成、コンテナランタイムバージョン </ins> * 問題を再現するための手順
Change:
This is a Feature Request What would you like to be Add hyperlink to RFC7468 under API-based signers section in . Why is this needed This Change will make easier for the users to easily know about RFC7468 Timestamp as a quick reference. Comments kind/feature
/assign
Fixed it here
It is always a good practice to work on those issues which have the tag .
/language en /priority backlog /triage accepted Thanks for the suggestion
Thanks for your suggestion, i will take care from next time.

Discussion:
``` Non-PEM content may appear before or after the CERTIFICATE PEM blocks and is unvalidated, <del> to allow for explanatory text as described in section 5.2 of RFC7468. </del> <ins> to allow for explanatory text as described in [section 5.2 of RFC7468](https://www.rfc-editor.org/rfc/rfc7468#section-5.2). </ins> When encoded in JSON or YAML, this field is base-64 encoded. A CertificateSigningRequest containing the example certificate above would look like this:
Change:
Problem: The text on should point to these Check the page for the problem. Page to Update: Proposed Solution: It should resolve this issue by adding a simple link and enhancing the document line. Update the link on the text Upstream Marketing Team to and not to this . /kind document /assign /language en
The label(s) cannot be applied, because the repository doesn't have them. <detailsIn response to : Problem: The text on should point to these Check the page for the problem. It should resolve this issue by adding a simple link and enhancing the document line. Update the link on the text Upstream Marketing Team to and not to this . /assign /language en Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details
/triage accepted

Discussion:
- Blog posts should be relevant to Kubernetes users. - Topics related to participation in or results of Kubernetes SIGs activities are always on <del> topic (see the work in the [Upstream Marketing Team](https://github.com/kubernetes/community/blob/master/communication/marketing-team/storytelling-resources/blog-guidelines.md#upstream-marketing-blog-guidelines) </del> <ins> topic (see the work in the [Contributor Comms Team](https://github.com/kubernetes/community/blob/master/communication/contributor-comms/storytelling-resources/blog-guidelines.md#upstream-marketing-blog-guidelines) </ins> for support on these posts). - The components of Kubernetes are purposely modular, so tools that use existing integration points like CNI and CSI are on topic.
Change:
This is a Bug Report <!-- Thanks for filing an issue! Before submitting, please fill in the following information. --<!-- See for guidance on writing an actionable issue description. --<!--Required Information--Problem: The page has a heading, , that isn't actually needed. Readers can work out that the page has an introduction by reading the text from the start. Typically, we don't start our document pages with a heading such as Introduction; instead, we have introductory text before the first heading. Proposed Solution: Delete the line from Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--Additional Information: /good-first-issue /language en If you have already worked on an issue and have had your change merged, please consider holding back on this one. That will let other, less experienced, contributors find this to work on it.
This request has been marked as suitable for new contributors. Please ensure that the issue body includes answers to the following questions: Why are we solving this issue? To address this issue, are there any code changes? If there are code changes, what needs to be done in the code and what places can the assignee treat as reference points? Does this issue have zero to low barrier of entry? How can the assignee reach out to you for help? For more details on the requirements of such an issue, please see and ensure that they are met. If this request no longer meets these requirements, the label can be removed by commenting with the command. <detailsIn response to : This is a Bug Report <!-- See for guidance on writing an actionable issue description. --Problem: The page has a heading, , that isn't actually needed. Proposed Solution: Delete the line from <!--Kubernetes Version:--/good-first-issue /language en </details
/triage accepted /priority backlog
/assign
I'm closing my PR and expecting new folks to actually contribute to fixing this minor issue. Feel free to raise a PR for this issue! /unassign
can I work on this issue! /assign

Discussion:
<!-- body --> <del> ## Introduction </del> Kubernetes DNS schedules a DNS Pod and Service on the cluster, and configures the kubelets to tell individual containers to use the DNS Service's IP to resolve DNS names.