jiebi/CodeConvo huggingface dataset:
Change:
`edit`        | <code>kubectl edit (-f FILENAME &#124; TYPE NAME &#124; TYPE/NAME) [flags]</code> | Edit and update the definition of one or more resources on the server by using the default editor. `events`      | `kubectl events` | List events `exec`        | `kubectl exec POD [-c CONTAINER] [-i] [-t] [flags] [-- COMMAND [args...]]` | Execute a command against a container in a pod. <del> `explain`    | `kubectl explain  [--recursive=false] [flags]` | Get documentation of various resources. For instance pods, nodes, services, etc. </del> <ins> `explain`    | `kubectl explain TYPE [--recursive=false] [flags]` | Get documentation of various resources. For instance pods, nodes, services, etc. </ins> `expose`        | <code>kubectl expose (-f FILENAME &#124; TYPE NAME &#124; TYPE/NAME) [--port=port] [--protocol=TCP&#124;UDP] [--target-port=number-or-name] [--name=name] [--external-ip=external-ip-of-service] [--type=type] [flags]</code> | Expose a replication controller, service, or pod as a new Kubernetes service. `get`        | <code>kubectl get (-f FILENAME &#124; TYPE [NAME &#124; /NAME &#124; -l label]) [--watch] [--sort-by=FIELD] [[-o &#124; --output]=OUTPUT_FORMAT] [flags]</code> | List one or more resources. `kustomize`    | `kubectl kustomize <dir> [flags] [options]` | List a set of API resources generated from instructions in a kustomization.yaml file. The argument must be the path to the directory containing the file, or a git repository URL with a path suffix specifying same with respect to the repository root.

Discussion:
This is a Bug Report Improvements needed on the page : <!--Required Information--Problem: On Section Explain and top syntax needs to be corrected. kubectl explain [--recursive=false] [flags] kubectl top [flags] [options] Some grammatical improvements needed in section. Proposed Solution: For operations: kubectl explain TYPE [--recursive=false] [flags] kubectl top POD/NODE [flags] [options] Page to Update: <!--Optional Information (remove the comment tags around the information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--
/language en /area kubectl
The label(s) cannot be applied, because the repository doesn't have them. <detailsIn response to : /language en /area kubectl 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 will be glad to contribute to the changes if triage is accepted.
Raised a reference
I agree we should update those commands, with out adding the parameters kubectl will just ask for them. I'm not sure of the exact grammatical errors you're referring to though. /triage accepted
Change:
investigate! Contact us on <del> [Slack](/docs/tasks/debug/overview/#slack) or </del> <ins> [Slack](https://slack.k8s.io/) or </ins> [Forum](https://discuss.kubernetes.io) or [GitHub](https://github.com/kubernetes/kubernetes). ## {{% heading "whatsnext" %}} <del> Visit the [troubleshooting overview document](/docs/tasks/debug/overview/) </del> <ins> Visit the [troubleshooting overview document](/docs/tasks/debug/) </ins> for more information.

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: On the page we find : 404 error in the section . The link is also wrong in the section, giving a 404 error. Proposed Solution: The proposed solution is to update the in the k/website repo. Do the following changes: Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--
/triage accepted /language en
I think new contributors can work on this issue. /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 : I think new contributors can work on this issue. /good-first-issue 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
Change:
are being moved to the [Tasks](/docs/tasks/), [Tutorials](/docs/tutorials/), and [Concepts](/docs/concepts) sections. The content in this topic has moved to: --> <del> Kubernetes文档中[使用手册](/zh/docs/user-guide/)部分中的主题被移动到 </del> <ins> Kubernetes文档中[用户指南](/zh/docs/user-guide/)部分中的主题被移动到 </ins> [任务](/zh/docs/tasks/)、[教程](/zh/docs/tutorials/)和[概念](/zh/docs/concepts)节。 本主题内容已移至:

Discussion:
This is a Bug Report In /content/zh/includes/user-guide-content- I think it's better to translate "user guide" into “”
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
File: /language zh
/assign
/triage accepted
The label cannot be applied. Only GitHub organization members can add the label. <detailsIn response to : /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
/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 : /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
/language zh /kind feature
Change:
--- <del> title: Kubelet 凭据提供程序（CredentialProvider）（v1beta1） </del> <ins> title: Kubelet CredentialProvider (v1beta1) </ins> content_type: tool-reference package: credentialprovider.kubelet.k8s.io/v1beta1 ---

Discussion:
Translate Chinese version for reference/config-api/kubelet- Comments /language zh /assign
/triage accepted
I think this issue can be included in next time.
Change:
该准入控制器 {{< glossary_tooltip text="污点" term_id="taint" >}} 新创建的 `NotReady` 和 `NoSchedule` 节点。 避免了可能导致 Pod 在更新其污点以准确反映其所报告状况之前，就安排了在新节点上的竞争条件的情况。 <del> ### ValidatingAdmissionWebhook {#validatingadmissionwebhook} {{< feature-state for_k8s_version="v1.13" state="beta" >}} </del> <ins> ### ValidatingAdmissionWebhook {#validatingadmissionwebhook} {{< feature-state for_k8s_version="v1.13" state="beta" >}} </ins> <!-- This admission controller calls any validating webhooks which match the request. Matching

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: Page /zh/docs/reference/access-authn-authz/admission-controllers/ display abnormally, these anchor points should start on a new line. Proposed Solution: fix the anchor point format. abnormal format: normal format: Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--
/assign /language zh
Change:
| 字段                  | 类型                                                                                                         | 解释                                                                               | |-----------------------|--------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------| <del> | namespace             | string                                                                                                       | 为所有资源添加名字看                                                     | </del> <ins> | namespace             | string                                                                                                       | 为所有资源添加名字空间                                                     | </ins> | namePrefix            | string                                                                                                       | 此字段的值将被添加到所有资源名称前面                     | | nameSuffix            | string                                                                                                       | 此字段的值将被添加到所有资源名称后面                      | | commonLabels          | map[string]string                                                                                            | 要添加到所有资源和选择算符的标签                                       |

Discussion:
There are some Chinese typo issues in , which should be corrected. For example: <img width="705" alt="image" src="https://user-"The "" should be "“. And, <img width="572" alt="image" src="https://user-"The "“ is wrong and should be "". As I have read the full article, I am planing to submit a PR.
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:
<ins> --- api_metadata: apiVersion: "" import: "k8s.io/api/core/v1" kind: "LocalObjectReference" content_type: "api_reference" description: "LocalObjectReference 包含足够的信息，可以让你在同一命名空间内找到引用的对象。" title: "LocalObjectReference" weight: 4 auto_generated: true --- <!-- api_metadata: apiVersion: "" import: "k8s.io/api/core/v1" kind: "LocalObjectReference" content_type: "api_reference" description: "LocalObjectReference contains enough information to let you locate the referenced object inside the same namespace." title: "LocalObjectReference" weight: 4 auto_generated: true --> `import "k8s.io/api/core/v1"` <!-- LocalObjectReference contains enough information to let you locate the referenced object inside the same namespace. --> LocalObjectReference 包含足够的信息，可以让你在同一命名空间（namespace）内找到引用的对象。 <hr> <!-- - **name** (string) Name of the referent. More info: https://kubernetes.io/docs/concepts/overview/working-with-objects/names/#names --> - **name** (string) 被引用者的名称。 更多信息: https://kubernetes.io/zh/docs/concepts/overview/working-with-objects/names/#names。 </ins>

Discussion:
This is a Bug Report Problem: do not have chinese docs: Proposed Solution: add chinese docs in website Comments /language zh /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:
<ins> apiVersion: v1 kind: Pod metadata: name: sa-token-test spec: containers: - name: container-test image: busybox volumeMounts: - name: token-vol mountPath: "/service-account" readOnly: true serviceAccountName: default volumes: - name: token-vol projected: sources: - serviceAccountToken: audience: api expirationSeconds: 3600 path: token </ins>

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. --Translate into Japanese. Why is this needed This page has not been translated. Comments <!-- Any additional related comments that might help. Drawings/mockups would be extremely helpful (if required). --/language ja /assign
/triage accepted
Change:
Kubernetes provides great primitives for deploying applications to a cluster: it can be as simple as `kubectl create -f app.yaml`. Deploy apps across multiple clusters has never been that simple. How should app workloads be distributed? Should the app resources be replicated into all clusters, replicated into selected clusters, or partitioned into clusters? How is  access to the clusters managed? What happens if some of the resources that a user wants to distribute pre-exist, in some or all of the clusters, in some form? <del> In SIG Multicluster, our journey has revealed that there are multiple possible models to solve these problems and there probably is no single best-fit, all-scenario solution. [Federation](/docs/concepts/cluster-administration/federation/), however, is the single biggest Kubernetes open source sub-project, and has seen the maximum interest and contribution from the community in this problem space. The project initially reused the Kubernetes API to do away with any added usage complexity for an existing Kubernetes user. This approach was not viable, because of the problems summarised below: </del> <ins> In SIG Multicluster, our journey has revealed that there are multiple possible models to solve these problems and there probably is no single best-fit, all-scenario solution. [Kubernetes Cluster Federation (KubeFed for short)](https://github.com/kubernetes-sigs/kubefed), however, is the single biggest Kubernetes open source sub-project, and has seen the maximum interest and contribution from the community in this problem space. The project initially reused the Kubernetes API to do away with any added usage complexity for an existing Kubernetes user. This approach was not viable, because of the problems summarised below: </ins> * Difficulties in re-implementing the Kubernetes API at the cluster level, as federation-specific extensions were stored in annotations. * Limited flexibility in federated types, placement and reconciliation, due to 1:1 emulation of the Kubernetes API.

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: Link for Federation in is broken Proposed Solution: Should be updated with correct link 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
/area blog
/assign
/language en
Change:
Любой код, больший или равный 200 и меньший 400, означает успех. Любой другой код интерпретируется как ошибка. Вы можете посмотреть исходные коды сервера в <del> [server.go](https://github.com/kubernetes/kubernetes/blob/{{< param "githubbranch" >}}/test/images/agnhost/liveness/server.go). </del> <ins> [server.go](https://github.com/kubernetes/kubernetes/blob/master/test/images/agnhost/liveness/server.go). </ins> В течение первых 10 секунд жизни контейнера обработчик `/healthz` возвращает статус 200. После обработчик возвращает статус 500.

Discussion:
This is a Bug Report Problem: Regarding , I found the similar broken links on other pages. English pages have already been fixed. ref: ru pages also need to be fixed. Proposed Solution: Fixes broken links including {{< param "githubbranch" }} to master. In the case of link to , fixes to {{< param "fullversion" }}. ref:
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
Change:
```json { <del> "auths": { "https://index.docker.io/v1/": { "username": "tiger", "password": "pass113", "email": "tiger@acme.com", "auth": "dGlnZXI6cGFzczExMw==" } } </del> <ins> "apiVersion": "v1", "data": { ".dockerconfigjson": "eyJhdXRocyI6eyJteS1yZWdpc3RyeTo1MDAwIjp7InVzZXJuYW1lIjoidGlnZXIiLCJwYXNzd29yZCI6InBhc3MxMTMiLCJlbWFpbCI6InRpZ2VyQGFjbWUuY29tIiwiYXV0aCI6ImRHbG5aWEk2Y0dGemN6RXhNdz09In19fQ==" }, "kind": "Secret", "metadata": { "creationTimestamp": "2021-07-01T07:30:59Z", "name": "secret-tiger-docker", "namespace": "default", "resourceVersion": "566718", "uid": "e15c1d7b-9071-4100-8681-f3a7a2ce89ca" }, "type": "kubernetes.io/dockerconfigjson" </ins> } ``` ### Basic authentication Secret

Discussion:
Doc link: ` I think it's more understandable by adding to this command the docker server (registry) Current version: kubectl create secret docker-registry secret-tiger-docker --docker-username=tiger --docker-password=pass113 --docker- New version: kubectl create secret docker-registry secret-tiger-docker --docker-username=tiger --docker-password=pass113 --docker- --docker-server=my-registry:5000
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 storage
/assign
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
Change:
kubectl get statefulset web ``` ``` <del> NAME      DESIRED   CURRENT   AGE web       2         1         20s </del> <ins> NAME   READY   AGE web    2/2     37s </ins> ``` ### Ordered Pod creation

Discussion:
I wish /docs/getting-started-guides/ listed both Ubuntu guides in the Bare Metal section, noting the networking for each (the listed one uses Flannel, the omitted one (but it is in the navigation panel on the left) uses Calico).
Ubuntu is getting a big rewrite as well.
Change:
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" %}}

Discussion:
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:
Change:
different when read back. * Setting originally unset fields is less likely to cause problems than overwriting fields set in the original request. Avoid doing the latter. <del> * This is a beta feature. Future versions of Kubernetes may restrict the types of mutations these webhooks can make. </del> * Future changes to control loops for built-in resources or third-party resources may break webhooks that work well today. Even when the webhook installation API is finalized, not all possible webhook behaviors will be guaranteed to be supported

Discussion:
This is a Bug Report It's not a bug, just an outdated doc thing. Problem: The MutatingWebhookConfiguration and ValidatingWebhookConfiguration APIs have been promoted to in . But the docs still show that they are in beta state at and . Proposed Solution: the description from the two plug-ins. the descriptions of the two plug-ins if they need an update too. Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--
I'm investigating this issue, hope I can send a PR for this after someone triaged/confirmed it. /assign
/triage accepted
Change:
</ul> <pre style="background-color:#fff"><span style="color:#000;font-weight:bold">apiVersion</span>:<span style="color:#bbb"> </span>kubeproxy.config.k8s.io/v1alpha1<span style="color:#bbb"> </span><span style="color:#bbb"></span><span style="color:#000;font-weight:bold">kind</span>:<span style="color:#bbb"> </span>KubeProxyConfiguration<span style="color:#bbb"> <del> </span><span style="color:#bbb"> </span><span style="color:#bbb">	</span>...<span style="color:#bbb"> </span><span style="color:#bbb"> </del> <ins> </span><span style="color:#bbb"></span>...<span style="color:#bbb"> </ins> </span></pre><p>The KubeProxyConfiguration type should be used to change the configuration passed to kube-proxy instances deployed in the cluster. If this object is not provided or provided only partially, kubeadm applies defaults.</p> <p>See https://kubernetes.io/docs/reference/command-line-tools-reference/kube-proxy/ or

Discussion:
The indentation of the example configuration is messy. !
/kind bug /language en page:
Also Consider to remove the exist in the same page under . Note: This page is automatically generated, you are not allowed to directly change the documentation page.
/retitle Messy indentation on kubeadm config reference page
/priority backlog We'd prioritize other improvements over this one. /triage accepted
/assign This is because the Golang source code contains TAB characters instead of SPACEs as a convention, and those TABs are messing up the YAML snippet. I'll work on this.
PR sent for website. PR sent for the generator.