jiebi/CodeConvo huggingface dataset:
Change:
Very basic step "Install kubectl binary with curl on Windows" Response seems good: But .exe is actually XML, giving download error: Hard to realize and quite unfriendly! Thanks
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
/kind bug There are multiple broken links on this page. It seems the links on this page is missing the version from it
/assign

Discussion:
Or if you have `curl` installed, use this command: ```powershell <del> curl -LO https://dl.k8s.io/release/{{< param "fullversion" >}}/bin/windows/amd64/kubectl.exe </del> <ins> curl -LO "https://dl.k8s.io/release/{{< param "fullversion" >}}/bin/windows/amd64/kubectl.exe" </ins> ``` {{< note >}}

Download the kubectl checksum file: ```powershell <del> curl -LO https://dl.k8s.io/{{< param "fullversion" >}}/bin/windows/amd64/kubectl.exe.sha256 </del> <ins> curl -LO "https://dl.k8s.io/{{< param "fullversion" >}}/bin/windows/amd64/kubectl.exe.sha256" </ins> ``` Validate the kubectl binary against the checksum file:

1. Download the latest release with the command: ```powershell <del> curl -LO https://dl.k8s.io/release/{{< param "fullversion" >}}/bin/windows/amd64/kubectl-convert.exe </del> <ins> curl -LO "https://dl.k8s.io/release/{{< param "fullversion" >}}/bin/windows/amd64/kubectl-convert.exe" </ins> ``` 1. Validate the binary (optional)

Download the kubectl-convert checksum file: ```powershell <del> curl -LO https://dl.k8s.io/{{< param "fullversion" >}}/bin/windows/amd64/kubectl-convert.exe.sha256 </del> <ins> curl -LO "https://dl.k8s.io/{{< param "fullversion" >}}/bin/windows/amd64/kubectl-convert.exe.sha256" </ins> ``` Validate the kubectl-convert binary against the checksum file:
Change:
Please provide links on the 'Before you begin' section, teaching how to 'have dynamic PersistentVolume provisioner with a default StorageClass'. I'm quite new to K8s and am not sure how to verify if I have the former half of this sentence, and the latter end of it (static provisioning) looks less automated / more difficult.
Seems like it could just link here:
If anyone does work on this, it's easier to review PRs that only touch a single localization.
/language en /triage accepted /priority backlog
do we have any section on dynamic PersistentVolume provisioner with a default StorageClass ?
Let's open that question up - anyone who wants to answer it is welcome to.
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]:
The Kubernetes project currently lacks enough active 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 Close this issue or PR with Offer to help out with [Issue Triage][1] Please send feedback to sig-contributor-experience at . /lifecycle rotten [1]:

Discussion:
<del> You need to either have a dynamic PersistentVolume provisioner with a default </del> <ins> You need to either have a [dynamic PersistentVolume provisioner](/docs/concepts/storage/dynamic-provisioning/) with a default </ins> [StorageClass](/docs/concepts/storage/storage-classes/), or [statically provision PersistentVolumes](/docs/user-guide/persistent-volumes/#provisioning) yourself to satisfy the [PersistentVolumeClaims](/docs/user-guide/persistent-volumes/#persistentvolumeclaims)
Change:
Problem: The link for Exemptions in is wrong and does not give any information about exemptions. The link used for it is: but there is no information or content of Exemptions in Enforce Pod Security Standards by Configuring the Built-in Admission Controller. The actual information for Exemptions is in the . Proposed Solution: We will have to use this link: for Exemptions instead of . Page to Update:
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
/sig security /sig auth
If it seems good then I'm up for it. /assign
Fixed it here:

Discussion:
As of v1.22, Kubernetes provides a built-in [admission controller](/docs/reference/access-authn-authz/admission-controllers/#podsecurity) to enforce the [Pod Security Standards](/docs/concepts/security/pod-security-standards). <del> You can configure this admission controller to set cluster-wide defaults and [exemptions](#exemptions). </del> <ins> You can configure this admission controller to set cluster-wide defaults and [exemptions](/docs/concepts/security/pod-security-admission/#exemptions). </ins> ## {{% heading "prerequisites" %}}
Change:
This is a Feature Request translate docs/reference/glossary/garbage- into Chinese. What would you like to be content/zh/docs/reference/glossary/garbage- /language zh /assign
/triage accepted

Discussion:
<ins> --- title: 垃圾收集 id: garbage-collection date: 2021-07-07 full_link: /zh/docs/concepts/workloads/controllers/garbage-collection/ short_description: > Kubernetes 用于清理集群资源的各种机制的统称。 aka: tags: - fundamental - operation --- <!-- title: Garbage Collection id: garbage-collection date: 2021-07-07 full_link: /docs/concepts/workloads/controllers/garbage-collection/ short_description: > A collective term for the various mechanisms Kubernetes uses to clean up cluster resources. aka: tags: - fundamental - operation --> <!-- Garbage collection is a collective term for the various mechanisms Kubernetes uses to clean up cluster resources. --> 垃圾收集是 Kubernetes 用于清理集群资源的各种机制的统称。 <!--more--> <!-- Kubernetes uses garbage collection to clean up resources like [unused containers and images](/docs/concepts/workloads/controllers/garbage-collection/#containers-images), [failed Pods](/docs/concepts/workloads/pods/pod-lifecycle/#pod-garbage-collection), [objects owned by the targeted resource](/docs/concepts/overview/working-with-objects/owners-dependents/), [completed Jobs](/docs/concepts/workloads/controllers/ttlafterfinished/), and resources that have expired or failed. --> Kubernetes 使用垃圾收集机制来清理资源，例如： [未使用的容器和镜像](/zh/docs/concepts/workloads/controllers/garbage-collection/#containers-images)、 [失败的 Pod](/zh/docs/concepts/workloads/pods/pod-lifecycle/#pod-garbage-collection)、 [目标资源拥有的对象](/zh/docs/concepts/overview/working-with-objects/owners-dependents/)、 [已完成的 Job](/zh/docs/concepts/workloads/controllers/ttlafterfinished/)、 过期或出错的资源。 </ins>  No newline at end of file
Change:
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
Link: /retitle [zh] Issue with /zh/docs/tutorials/stateful-application/basic-stateful-set
/assign

Discussion:
demonstrates how to create, delete, scale, and update the Pods of StatefulSets. --> <del> 本教程介绍如何了使用 [StatefulSets](/zh/docs/concepts/workloads/controllers/statefulset/) 来管理应用。 </del> <ins> 本教程介绍了如何使用 [StatefulSets](/zh/docs/concepts/workloads/controllers/statefulset/) 来管理应用。 </ins> 演示了如何创建、删除、扩容/缩容和更新 StatefulSets 的 Pods。

* [Cluster DNS](/zh/docs/concepts/services-networking/dns-pod-service/) * [Headless Services](/zh/docs/concepts/services-networking/service/#headless-services) * [PersistentVolumes](/zh/docs/concepts/storage/persistent-volumes/) <del> * [PersistentVolume Provisioning](https://github.com/kubernetes/examples/tree/{{< param "githubbranch" >}}/staging/persistent-volume-provisioning/) </del> <ins> * [PersistentVolume Provisioning](https://github.com/kubernetes/examples/tree/master/staging/persistent-volume-provisioning/) </ins> * [StatefulSets](/zh/docs/concepts/workloads/controllers/statefulset/) * [kubectl CLI](/zh/docs/user-guide/kubectl/)
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: mentions an annotation prefix that is deprecated / not actually official. Proposed Solution: Remove all mention of annotations from that page. Page to Update: and specifically Additional Information: This is a follow-up to /language en
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
/retitle Remove labels from ”Autoscale the DNS Service in a Cluster”
/assign

Discussion:
metadata: name: kube-dns-autoscaler namespace: kube-system <del> labels: addonmanager.kubernetes.io/mode: Reconcile </del> --- kind: ClusterRole apiVersion: rbac.authorization.k8s.io/v1 metadata: name: system:kube-dns-autoscaler <del> labels: addonmanager.kubernetes.io/mode: Reconcile </del> rules: - apiGroups: [""] resources: ["nodes"]

apiVersion: rbac.authorization.k8s.io/v1 metadata: name: system:kube-dns-autoscaler <del> labels: addonmanager.kubernetes.io/mode: Reconcile </del> subjects: - kind: ServiceAccount name: kube-dns-autoscaler

labels: k8s-app: kube-dns-autoscaler kubernetes.io/cluster-service: "true" <del> addonmanager.kubernetes.io/mode: Reconcile </del> spec: selector: matchLabels:
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 <!-- Describe as precisely as possible how this feature/enhancement should work from the user perspective. What should be changed, etc. --It is about this page. I guess that Links to can be replaced with . Why is this needed has already been translated into Japanese. Comments /language ja where to update <!-- Any additional related comments that might help. Drawings/mockups would be extremely helpful (if required). --
/triage accepted
/assign

Discussion:
## {{% heading "whatsnext" %}} <del> 独自のクラウドコントローラーマネージャーを構築および開発するには[クラウドコントローラーマネージャーの開発](/docs/tasks/administer-cluster/developing-cloud-controller-manager.md)を参照してください。 </del> <ins> 独自のクラウドコントローラーマネージャーを構築および開発するには[クラウドコントローラーマネージャーの開発](/ja/docs/tasks/administer-cluster/developing-cloud-controller-manager/)を参照してください。 </ins>
Change:
says: Pod's DNS Policy : The Pod inherits the name resolution configuration from the node that the pods run on. See related discussion for more details. “Related discussion” is a hyperlink to : Any DNS query that does not match the configured cluster domain suffix, such as "", is forwarded to the upstream nameserver inherited from the node. Cluster administrators may have extra stub-domain and upstream DNS servers configured. See related discussion for details on how DNS queries are handled in those cases. “Related discussion” is a hyperlink to Both hyper targets do not exist in the destination webpage (so that the browser scrolls to the right place). contains a hyperlink “See Inheriting DNS from the node” → , which as above does not exist.
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
/sig docs

Discussion:
- "`Default`": The Pod inherits the name resolution configuration from the node that the pods run on. <del> See [related discussion](/docs/tasks/administer-cluster/dns-custom-nameservers/#inheriting-dns-from-the-node) </del> <ins> See [related discussion](/docs/tasks/administer-cluster/dns-custom-nameservers) </ins> for more details. - "`ClusterFirst`": Any DNS query that does not match the configured cluster domain suffix, such as "`www.kubernetes.io`", is forwarded to the upstream nameserver inherited from the node. Cluster administrators may have extra stub-domain and upstream DNS servers configured. <del> See [related discussion](/docs/tasks/administer-cluster/dns-custom-nameservers/#effects-on-pods) </del> <ins> See [related discussion](/docs/tasks/administer-cluster/dns-custom-nameservers) </ins> for details on how DNS queries are handled in those cases. - "`ClusterFirstWithHostNet`": For Pods running with hostNetwork, you should explicitly set its DNS policy "`ClusterFirstWithHostNet`".

### Check the local DNS configuration first Take a look inside the resolv.conf file. <del> (See [Inheriting DNS from the node](/docs/tasks/administer-cluster/dns-custom-nameservers/#inheriting-dns-from-the-node) and </del> <ins> (See [Customizing DNS Service](/docs/tasks/administer-cluster/dns-custom-nameservers) and </ins> [Known issues](#known-issues) below for more information) ```shell
Change:
says: typo gll → all
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

Discussion:
<td colspan="2">--address string&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Default: 0.0.0.0 </td> </tr> <tr> <del> <td></td><td style="line-height: 130%; word-wrap: break-word;">The IP address for the Kubelet to serve on (set to <code>0.0.0.0</code> or <code>::</code> for listening in gll interfaces and IP families)  (DEPRECATED: This parameter should be set via the config file specified by the Kubelet's <code>--config</code> flag. See https://kubernetes.io/docs/tasks/administer-cluster/kubelet-config-file/ for more information.)</td> </del> <ins> <td></td><td style="line-height: 130%; word-wrap: break-word;">The IP address for the Kubelet to serve on (set to <code>0.0.0.0</code> or <code>::</code> for listening in all interfaces and IP families)  (DEPRECATED: This parameter should be set via the config file specified by the Kubelet's <code>--config</code> flag. See https://kubernetes.io/docs/tasks/administer-cluster/kubelet-config-file/ for more information.)</td> </ins> </tr> <tr>
Change:
broken link in page:
/kind bug /sig windows /language en /triage accepted /priority backlog Thanks for the report
Would like to work on this issue /assign

Discussion:
Information on the different Windows Server servicing channels including their support models can be found at <del> [Windows Server servicing channels](https://docs.microsoft.com/en-us/windows-server/get-started-19/servicing-channels-19). </del> <ins> [Windows Server servicing channels](https://docs.microsoft.com/en-us/windows-server/get-started/servicing-channels-comparison). </ins>
Change:
This is a Bug Report <!--Required Information--Problem: The code link mention under the in the redirect to the code of k8s version v1.15.0 i.e. instead of the master i.e. . Also, the code in the master is modified as compared to the code in v1.15.0. Proposed Solution: The code link redirects to instead of . Page to Update:
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
/sig auth /sig api-machinery
I'm up for it. /assign
Fixed it here:
/remove-kind bug /kind cleanup /language en /sig auth

Discussion:
the [deployment API](/docs/reference/generated/kubernetes-api/{{< param "version" >}}/#deployment-v1-apps). The test also creates a [service](/docs/reference/generated/kubernetes-api/{{< param "version" >}}/#service-v1-core) as the front-end of the webhook server. See <del> [code](https://github.com/kubernetes/kubernetes/blob/v1.15.0/test/e2e/apimachinery/webhook.go#L301). </del> <ins> [code](https://github.com/kubernetes/kubernetes/blob/v1.22.0/test/e2e/apimachinery/webhook.go#L748). </ins> You may also deploy your webhooks outside of the cluster. You will need to update your webhook configurations accordingly.
Change:
says: It should be AN upgrade.
/triage accepted /sig cluster-lifecycle /help
This request has been marked as needing help from a contributor. 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 : /triage accepted /sig cluster-lifecycle /help </details
/good-first-issue
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 : /good-first-issue </details
Thanks for reporting. I am willing to fix this issue. /assign
/language en
Should I work on this issue
/assign

Discussion:
## kubeadm upgrade guidance <del> The steps for performing a upgrade using kubeadm are outlined in [this document](/docs/tasks/administer-cluster/kubeadm/kubeadm-upgrade/). </del> <ins> The steps for performing an upgrade using kubeadm are outlined in [this document](/docs/tasks/administer-cluster/kubeadm/kubeadm-upgrade/). </ins> For older versions of kubeadm, please refer to older documentation sets of the Kubernetes website. You can use `kubeadm upgrade diff` to see the changes that would be applied to static pod manifests.
Change:
says: the “configuration format” is a hyperlink to , it shall instead point to (beta2 → beta3) says: where “NodeRegistrationOptions” is a hyperlink to . It shall instead point to (beta2 → beta3) says: where “configuration file” is a hypelink to . It shall instead point to (beta2 → beta3) says: where “API referenc” is a hyperlink to It shall instead point to .
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
/sig cluster-lifecycle /remove-kind bug /kind cleanup
/language en

Discussion:
the [kubeadm config migrate](/docs/reference/setup-tools/kubeadm/kubeadm-config/) command. For more information on the fields and usage of the configuration you can navigate to our <del> [API reference](/docs/reference/config-api/kubeadm-config.v1beta2/). </del> <ins> [API reference](/docs/reference/config-api/kubeadm-config.v1beta3/). </ins> ## {{% heading "whatsnext" %}}

* [Validate IPv4/IPv6 dual-stack](/docs/tasks/network/validate-dual-stack) networking * Read about [Dual-stack](/docs/concepts/services-networking/dual-stack/) cluster networking <del> * Learn more about the kubeadm [configuration format](/docs/reference/config-api/kubeadm-config.v1beta2/) </del> <ins> * Learn more about the kubeadm [configuration format](/docs/reference/config-api/kubeadm-config.v1beta3/) </ins>

When using DigitalOcean, it can be the public one (assigned to `eth0`) or the private one (assigned to `eth1`) should you want to use the optional private network. The `kubeletExtraArgs` section of the kubeadm <del> [`NodeRegistrationOptions` structure](/docs/reference/config-api/kubeadm-config.v1beta2/#kubeadm-k8s-io-v1beta2-NodeRegistrationOptions) </del> <ins> [`NodeRegistrationOptions` structure](/docs/reference/config-api/kubeadm-config.v1beta3/#kubeadm-k8s-io-v1beta3-NodeRegistrationOptions) </ins> can be used for this. Then restart `kubelet`:

`--apiserver-extra-args "enable-admission-plugins=LimitRanger,enable-admission-plugins=NamespaceExists"` but this will result in the key `enable-admission-plugins` only having the value of `NamespaceExists`. <del> A known workaround is to use the kubeadm [configuration file](/docs/reference/config-api/kubeadm-config.v1beta2/). </del> <ins> A known workaround is to use the kubeadm [configuration file](/docs/reference/config-api/kubeadm-config.v1beta3/). </ins> ## kube-proxy scheduled before node is initialized by cloud-controller-manager
Change:
!
/triage accepted Would you like propose a fix?
/language zh
/kind bug (right?)
Please delete this symbol. !
I have already apply a pull request.

Discussion:
[certified platforms](/docs/setup/production-environment/turnkey-solutions/). There are also other standardized and custom solutions across a wide range of cloud and bare metal environments. <del> -->。 </del> <ins> --> </ins> 可以[下载 Kubernetes](/releases/download/)，在本地机器、云或你自己的数据中心上部署 Kubernetes 集群。 如果你不想自己管理 Kubernetes 集群，则可以选择托管服务，包括[经过认证的平台](/zh/docs/setup/production-environment/turnkey-solutions/)。 在各种云和裸机环境中，还有其他标准化和定制的解决方案。