jiebi/CodeConvo huggingface dataset:
Change:
image: redis:3.2-alpine ``` <del> ウェブサーバーのDeploymentを記載した以下のyamlファイルには、`podAntiAffinity` と`podAffinity`が設定されています。 全てのレプリカが`app=store`のラベルが付与されたPodと同じゾーンで稼働するよう、スケジューラーに設定されます。 また、それぞれのウェブサーバーは1つのノードで稼働されないことも保証されます。 </del> <ins> 次のウェブサーバーのDeployment例では、`app=web-store`ラベルが付与されたレプリカを作成します。Podアフィニティルールは、各レプリカを、`app=store`ラベルが付与されたPodを持つNodeに配置するようスケジューラーに指示します。Podアンチアフィニティルールは、1つのNodeに複数の`app=web-store`サーバーを配置しないようにスケジューラーに指示します。 </ins> ```yaml apiVersion: apps/v1

Discussion:
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 <!-- Describe as precisely as possible how this feature/enhancement should work from the user perspective. What should be changed, etc. --Updated Japanese translation for the file. Why is this needed There are several updates in and therefore this page is outdated. Comments <!-- Any additional related comments that might help. Drawings/mockups would be extremely helpful (if required). --/language ja /assign
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
Change:
上記の設定ファイルは、`dev-ramp-up`というコンテキストを表します。 <del> ## KUBECONFIG環境変数を設定する </del> <ins> ## KUBECONFIG環境変数を設定する {#set-the-kubeconfig-environment-variable} </ins> `KUBECONFIG`という環境変数が存在するかを確認してください。もし存在する場合は、後で復元できるようにバックアップしてください。例えば:

Discussion:
This is a Feature Request What would you like to be Translate into Japanese. Why is this needed This page has not been translated. Comments /language ja /assign
/triage accepted
Change:
``` 1. Verify the stored Secret is prefixed with `k8s:enc:aescbc:v1:` which indicates <del> the `aescbc` provider has encrypted the resulting data. </del> <ins> the `aescbc` provider has encrypted the resulting data. Confirm that the key name shown in `etcd` matches the key name specified in the `EncryptionConfiguration` mentioned above. In this example, you can see that the encryption key named `key1` is used in `etcd` and in `EncryptionConfiguration`. </ins> 1. Verify the Secret is correctly decrypted when retrieved via the API:

Discussion:
I propose adding one more best practice to “Encrypting Secret Data at Rest”: manually verify that the key used to encrypt secrets in etcd match the key that is saved to disk. Race conditions, bugs in the code, or user mistakes can overwrite with the wrong key. While the chances of this happening are small, it does happen and the consequences can be devastating. A best practice would be to verify that the keys match. Here are several such bugs: (Subscription required) As I said, these bugs are rare but will be devastating. We ran into this on a production cluster and very nearly lost the cluster. In our case, showed one key but we saw that was using a different, older key to encrypt secrets. The key in memory and the key on disk were different, and determining that required some very advanced troubleshooting. If all API servers are rebooted, the key will be lost and the secrets along with the key.
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
/label language/en
The label(s) cannot be applied. These labels are supported: . Is this label configured under or in ? <detailsIn response to : /label 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
/sig security
Change:
- `KubeletCredentialProviders`: Enable kubelet exec credential providers for image pull credentials. - `KubeletPluginsWatcher`: Enable probe-based plugin watcher utility to enable kubelet to discover plugins such as [CSI volume drivers](/docs/concepts/storage/volumes/#csi). <del> - `KubeletPodResources`: Enable the kubelet's pod resources GRPC endpoint. See [Support Device Monitoring](https://github.com/kubernetes/enhancements/blob/master/keps/sig-node/compute-device-assignment.md) </del> <ins> - `KubeletPodResources`: Enable the kubelet's pod resources gRPC endpoint. See [Support Device Monitoring](https://github.com/kubernetes/enhancements/blob/master/keps/sig-node/606-compute-device-assignment/README.md) </ins> for more details. - `LegacyNodeRoleBehavior`: When disabled, legacy behavior in service load balancers and node disruption will ignore the `node-role.kubernetes.io/master` label in favor of the

Discussion:
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--Proposed Solution: in this page is linked to a dead url. Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--
/kind bug /sig node /language en /triage accepted Rather than linking to a KEP, we should really add a new page to the documentation (maybe in Concepts, maybe in Reference) and then link to that.
The fail link in Support Device Monitoring due to . This root cause in the kind/bug is the repo of kubernetes/enhancements url that move to . I had a look at it and sent in a pull request for fix this.(PR ) /assign
/close
Closing this issue. <detailsIn response to : /close 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
Change:
Use the following commands to delete the StatefulSet. ```console <del> $ grace=$(kubectl get po cassandra-0 --template '{{.spec.terminationGracePeriodSeconds}}')  </del> <ins> $ grace=$(kubectl get po cassandra-0 -o=jsonpath='{.spec.terminationGracePeriodSeconds}')  </ins> && kubectl delete statefulset -l app=cassandra  && echo "Sleeping $grace"  && sleep $grace 

Discussion:
<!-- Thanks for filing an issue! Before submitting, please fill in the following information. --<!--Required Information--This is a... <!-- choose one by changing [ ] to [x] --- [ ] Feature Request [X] Bug Report Problem: There is a warning during the Netlify preview build process: Looks like liquid is trying to parse in the line: Proposed Solution: Find out how to escape in a code block for Liquid. Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--Kubernetes 1.6 <!--Additional Information:--
Change:
{{< note >}} Para descargar una versión específica, reemplace el `$(curl -L -s https://dl.k8s.io/release/stable.txt)` parte del comando con la versión específica. <del> Por ejemplo, para descargar la versión {{< param "fullversion" >}} en Intel macOS, escriba: </del> <ins> Por ejemplo, para descargar la versión {{< skew currentPatchVersion >}} en Intel macOS, escriba: </ins> ```bash <del> curl -LO "https://dl.k8s.io/release/{{< param "fullversion" >}}/bin/darwin/amd64/kubectl" </del> <ins> curl -LO "https://dl.k8s.io/release/v{{< skew currentPatchVersion >}}/bin/darwin/amd64/kubectl" </ins> ``` Y para macOS en Apple Silicon, escriba: ```bash <del> curl -LO "https://dl.k8s.io/release/{{< param "fullversion" >}}/bin/darwin/arm64/kubectl" </del> <ins> curl -LO "https://dl.k8s.io/release/v{{< skew currentPatchVersion >}}/bin/darwin/arm64/kubectl" </ins> ``` {{< /note >}}

Discussion:
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 param is deprecated. Proposed Solution: Replace the shortcode (Spanish pages), for example with or something close. <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--Part of /language es
/triage accepted /area localization /priority backlog
Change:
<ins> --- title: क्यूबएडीएम (Kubeadm) id: kubeadm date: 2018-04-12 full_link: /docs/admin/kubeadm/ short_description: > कुबेरनेट्स को जल्दी से इंस्टॉल करने और एक सुरक्षित क्लस्टर स्थापित करने के लिए एक उपकरण। aka: tags: - tool - operation --- कुबेरनेट्स को जल्दी से इंस्टॉल करने और एक सुरक्षित क्लस्टर स्थापित करने के लिए एक उपकरण। <!--more--> आप कंट्रोल प्लेन और {{< glossary_tooltip text="वर्कर नोड्स" term_id="node" >}} दोनों घटकों को स्थापित करने के लिए क्यूबएडीएम का उपयोग कर सकते हैं। </ins>

Discussion:
If this is your first contribution, visit for information on how to get started. Review a few to see which content you have to change and which you leave unchanged. Make sure your base, target branch is and create a working branch called . Create a file called Copy the content of to the file you created Localize the content. Push your change and create a pull request. Completing this feature issue fixes part of /language hi /triage accepted
/assign Thank you
Change:
All of this is best illustrated by examples.  Imagine a Kubernetes release, version X, which introduces a new API group.  A new Kubernetes release is made <del> every approximately 3 months (4 per year).  The following table describes which </del> <ins> every approximately 4 months (3 per year).  The following table describes which </ins> API versions are supported in a series of subsequent releases. <table>

Discussion:
In k8s document page: Second paragraph below Rule b says: All of this is best illustrated by examples. Imagine a Kubernetes release, version X, which introduces a new API group. A new Kubernetes release is made every approximately 3 months (4 per year). It should say: All of this is best illustrated by examples. Imagine a Kubernetes release, version X, which introduces a new API group. A new Kubernetes release is made every approximately 4 months (3 per year).
/kind bug /retitle Kubernetes Deprecation Policy page lists wrong release cadence /language en /help /priority backlog /triage accepted Thanks for the report.
This request has been marked as needing help from a contributor. Please ensure the request meets the requirements listed . If this request no longer meets these requirements, the label can be removed by commenting with the command. <detailsIn response to : /kind bug /retitle Kubernetes Deprecation Policy page lists wrong release cadence /language en /help /priority backlog /triage accepted 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
I would like to pick this up /assign
Change:
To enable swap on a node, the `NodeSwap` feature gate must be enabled on the kubelet, and the `--fail-swap-on` command line flag or `failSwapOn` <del> [configuration setting](/docs/reference/config-api/kubelet-config.v1beta1/#kubelet-config-k8s-io-v1beta1-KubeletConfiguration) </del> <ins> [configuration setting](/docs/reference/config-api/kubelet-config.v1beta1/) </ins> must be set to false. {{< warning >}}

Discussion:
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: Url selector #kubelet-config-k8s-io-v1beta1-KubeletConfiguration doesn't make a difference between: and Proposed Solution: Removing the selector from the URLs Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--
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
/retitle Problems with (generated) reference for kubelet configuration
Change:
Deployments and Services. See [Use a Service to Access an Application in a Cluster](/docs/tasks/access-application-cluster/service-access-application-cluster/) for an example.

Discussion:
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 describes a bug in Kubernetes where YAML 1.2 documents are not parsed (Kubernetes does not have good support for YAML 1.1), but then also Kubernetes does incorrectly parse completely valid YAML 1.1 the way that the specification defines. Why is this needed The bug makes it hard for some people, using conformant libraries, to make YAML documents that Kubernetes accepts. We should document the bug so that readers are aware of the shortcomings here. Comments /wg api-expression /language en /priority backlog
/triage accepted
i can help you because I'm new to it so if i can tag along i will be able to learn a lot
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]:
/remove-lifecycle stale
would you add this as a warning note in ?
/assign
Change:
[javascript_required] other = "JavaScript must be [enabled](https://www.enable-javascript.com/) to view this content" <del> [katacoda_removal_warning] other = """This online tutorial on this page uses functionality that will [not be available](https://www.oreilly.com/online-learning/leveraging-katacoda-technology.html) past <time datetime="2022-06-15">June 15th, 2022</time>.""" </del> [latest_release] other = "Latest Release:"

Discussion:
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: We a banner: Given the latest updates from O'Reilly, that banner may not be accurate and the service (albeit possibly degraded?) is expected to survive beyond June 15th 2022. Example page: Relevant to issue
we could remove the banner and wait till June 15. If a new update came then we can update it?
I'm OK with removing the banner.
/assign
/triage accepted
Change:
| `persistentvolumes` | `pv` | | false | PersistentVolume | | `pods` | `po` | | true | Pod | | `podtemplates` | | | true | PodTemplate | <del> | `replicationcontrollers` | `rc` | | true| ReplicationController | </del> <ins> | `replicationcontrollers` | `rc` | | true | ReplicationController | </ins> | `resourcequotas` | `quota` | | true | ResourceQuota | | `secrets` | | | true | Secret | | `serviceaccounts` | `sa` | | true | ServiceAccount | | `services` | `svc` | | true | Service | | `mutatingwebhookconfigurations` | | admissionregistration.k8s.io | false | MutatingWebhookConfiguration | | `validatingwebhookconfigurations` | | admissionregistration.k8s.io | false | ValidatingWebhookConfiguration | <del> | `customresourcedefinitions` | `crd`, `crds` | apiextensions.k8s.io | false |  CustomResourceDefinition | </del> <ins> | `customresourcedefinitions` | `crd,crds` | apiextensions.k8s.io | false | CustomResourceDefinition | </ins> | `apiservices` | | apiregistration.k8s.io | false | APIService | | `controllerrevisions` | | apps | true | ControllerRevision | | `daemonsets` | `ds` | apps | true | DaemonSet |

Discussion:
This is a Bug Report Problem: The resource type list on is about v1.13.3 which is too old. We are not obliged to keep the list updated on every release, but having the list updated to a supported version is still desireable. Proposed Solution: Update the list to reflect what we have today. Page to Update:
ref:
/assign
fixed. /close
Closing this issue. <detailsIn response to : fixed. /close 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
Change:
<!--more--> <!-- <del> Kubernetes supports several container runtimes: [Docker](http://www.docker.com), [containerd](https://containerd.io), [cri-o](https://cri-o.io/), [rktlet](https://github.com/kubernetes-incubator/rktlet) and any implementation of the [Kubernetes CRI (Container Runtime Interface)](https://github.com/kubernetes/community/blob/master/contributors/devel/sig-node/container-runtime-interface.md). </del> <ins> Kubernetes supports several container runtimes: {{< glossary_tooltip term_id="docker">}}, {{< glossary_tooltip term_id="containerd" >}}, {{< glossary_tooltip term_id="cri-o" >}}, and any implementation of the [Kubernetes CRI (Container Runtime Interface)](https://github.com/kubernetes/community/blob/master/contributors/devel/sig-node/container-runtime-interface.md). </ins> --> <del> Kubernetes 支持多个容器运行环境: [Docker](http://www.docker.com)、 [containerd](https://containerd.io)、[cri-o](https://cri-o.io/)、 [rktlet](https://github.com/kubernetes-incubator/rktlet) 以及任何实现 [Kubernetes CRI (容器运行环境接口)](https://github.com/kubernetes/community/blob/master/contributors/devel/sig-node/container-runtime-interface.md)。 </del> <ins> Kubernetes 支持多个容器运行环境: {{< glossary_tooltip term_id="docker">}}、 {{< glossary_tooltip term_id="containerd" >}}、{{< glossary_tooltip term_id="cri-o" >}} 以及任何实现 [Kubernetes CRI (容器运行环境接口)](https://github.com/kubernetes/community/blob/master/contributors/devel/sig-node/container-runtime-interface.md)。 </ins>

Discussion:
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: Clicking the "" hyperlink leads to the 404 page. <img width="876" alt="WeChatc2b6a16c89afc8d1086c8c92a0a7f437" src="https://user-"Proposed Solution: correct link as below: full_link: /docs/setup/production-environment/container-runtimes <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--
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
/assign
/language zh
Change:
<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>

Discussion:
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
Change:
# DO NOT REMOVE THIS (contact @kubernetes/sig-docs-leads) publish = "public" command = "git submodule update --init --recursive --depth 1 && make production-build" <ins> # adding in headers to prevent clickjacking [[headers]] for = "/*" [headers.values] X-Frame-Options = "DENY" X-XSS-Protection = "1; mode=block" </ins>

Discussion:
This is a Bug Report Problem: The entire website is currently vunerable to clickjacking due to not having a proper header. This issue came to our attention via an email to the Code of Conduct Committee inbox. For more information on what a clickjacking attack is, see the following: Proposed Solution(s): Option 1: Easy, but not supported by all browsers Add a header to I recommend we use to do this, as that's simplest. This has the advantage of being easy to implement on a static site, but isn't supported by all browsers (yet). I think we should implement it regardless, and assume that it will be supported by all browsers in the near future. Option 2: more complicated, but currently supported Set an header. We need to do this : What to allow: In both cases, we want to allow at least the following: Any CDN we pull javascript from Any CDN we pull CSS from Youtube Google Analytics Discourse twitter Google Calendar I suspect there's more and I'm just not remembering it though.
/priority important-soon /triage accepted
/help
This request has been marked as needing help from a contributor. Please ensure the request meets the requirements listed . If this request no longer meets these requirements, the label can be removed by commenting with the command. <detailsIn response to : /help 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
/assign I feel like this has come up before in another issue. Will do some looking...
Also see
We could also set to allow frames; that feels like it would be OK.