jiebi/CodeConvo huggingface dataset:
Code change:
hello world ``` <del> ``` </del> <ins> ```shell </ins> # we can "uninstall" a plugin, by simply removing it from our PATH sudo rm /usr/local/bin/kubectl-hello ```

Related discussion:
text: 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: line 35~39, there are extra spaces(more than 4 spaces) in front of shell box. line 427~430, it should be a shell box. So, we need shell code. line 445~451, it should be a shell box. So, we need shell code. Proposed Solution: [1] : Specifies the . Resource types are case-insensitive and you can specify the singular, plural, or abbreviated forms. For example, the following commands produce the same output: [2] [3] Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--/language en
/assign
Code change:
<ins> --- title: "zsh 自动补全" description: "zsh 自动补全的一些可选配置" headless: true --- <!-- --- title: "zsh auto-completion" description: "Some optional configuration for zsh auto-completion." headless: true --- --> <!-- The kubectl completion script for Zsh can be generated with the command `kubectl completion zsh`. Sourcing the completion script in your shell enables kubectl autocompletion. To do so in all your shell sessions, add the following to your `~/.zshrc` file: --> kubectl 通过命令 `kubectl completion zsh` 生成 Zsh 自动补全脚本。 在 shell 中导入（Sourcing）该自动补全脚本，将启动 kubectl 自动补全功能。 为了在所有的 shell 会话中实现此功能，请将下面内容加入到文件 `~/.zshrc` 中。 ```zsh source <(kubectl completion zsh) ``` <!-- If you have an alias for kubectl, you can extend shell completion to work with that alias: --> 如果你为 kubectl 定义了别名，可以扩展脚本补全，以兼容该别名。 ```zsh echo 'alias k=kubectl' >>~/.zshrc echo 'complete -F __start_kubectl k' >>~/.zshrc ``` <!-- After reloading your shell, kubectl autocompletion should be working. If you get an error like `complete:13: command not found: compdef`, then add the following to the beginning of your `~/.zshrc` file: --> 重新加载 shell 后，kubectl 自动补全功能将立即生效。 如果你收到 `complete:13: command not found: compdef` 这样的错误提示，那请将下面内容添加到 `~/.zshrc` 文件的开头： ```zsh autoload -Uz compinit compinit ``` </ins>

Related discussion:
text: This is a Feature Request translate content/docs/tasks/tools/install-kubectl- into Chinese What would you like to be content/zh/docs/tasks/tools/install-kubectl- /assign /language zh
/triage accepted
Code change:
* `apiserver_flowcontrol_current_inqueue_requests` is a gauge vector holding the instantaneous number of queued (not executing) requests, <del> broken down by the labels `priorityLevel` and `flowSchema`. </del> <ins> broken down by the labels `priority_level` and `flow_schema`. </ins> * `apiserver_flowcontrol_current_executing_requests` is a gauge vector holding the instantaneous number of executing (not waiting in a <del> queue) requests, broken down by the labels `priorityLevel` and `flowSchema`. </del> <ins> queue) requests, broken down by the labels `priority_level` and `flow_schema`. </ins> * `apiserver_flowcontrol_priority_level_request_count_samples` is a histogram vector of observations of the then-current number of requests broken down by the labels `phase` (which takes on the <del> values `waiting` and `executing`) and `priorityLevel`.  Each </del> <ins> values `waiting` and `executing`) and `priority_level`.  Each </ins> histogram gets observations taken periodically, up through the last activity of the relevant sort.  The observations are made at a high rate.

Related discussion:
text: Keep the doc consistent with
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
Code change:
If you need access to multiple registries, you can create one secret for each registry. <del> Kubelet will merge any `imagePullSecrets` into a single virtual `.docker/config.json` </del> ## {{% heading "whatsnext" %}}

Related discussion:
text: Ref: needs a rewrite. It mentions Docker (and Podman!) all over the place, which is a good indication that the docs are old enough to need a rewrite. At a minimum, remove mentions of Docker in these topics: /triage accepted /milestone 1.24
/assign
/assign
Reasked folks in Slack for correct disposition
Asked in the SIG Node slack channel:
To summarize the consensus from talking with folks about this issue, specifically the examples in Using a Private Registry section: The steps in the Using a Private Registry section are still valid. However, as written, it makes it sound like Docker is the only/recommended way to do this-which we dont want. We should be able to remove the docker examples and point folks to this page , which covers most of the same content with third party disclaimers already written into the examples. I plan to open a PR later this week with these changes!
Has anyone opened a PR for this issue? It seems to be referring to
Code change:
abstract: "자동화된 컨테이너 배포, 스케일링과 관리" cid: home --- <del> {{< announcement >}} {{< deprecationwarning >}} </del> {{< blocks/section id="oceanNodes" >}} {{% blocks/feature image="flower" %}}

Related discussion:
text: Umbrella issue: Remove the following from L6-8:
/kind cleanup
/language ko
/assign
This issue is included in also.
Code change:
# replace <node-to-drain> with the name of your node kubectl uncordon <node-to-drain> ``` <ins> ## {{% heading "whatsnext" %}} * See how to [Upgrade Linux nodes](/docs/tasks/administer-cluster/kubeadm/upgrading-linux-nodes/). </ins>

Related discussion:
text: 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 page titled “Upgrading Linux Nodes” Why is this needed We have an for Windows. Someone who runs Linux worker nodes may well want to see a page just like that, but explaining what to do for their Linux-based node OS. It is OK to adapt existing pages and to link to them. Comments /sig cluster-lifecycle /priority backlog /language en
Hi there is a section on in the , which has the content for upgrading Linux worker nodes. I wonder do you want a separate document for it?
Yes. This issue is a request for a document just like but with Linux in the title. It is OK to adapt existing pages and to link to them.
right, i can recall the section only says: From the Windows node, upgrade kubeadm: and no addition for another os. This will be helpful. are you working on it?
Thanks, for the information!
Hi thanks for your comments. Yeah, I am working on it. I will soon open a PR for it.
/assign
/triage accepted
I have raised a PR: Please take a look!
Code change:
Inspecting the logs for docker may also be useful: ```sh <del> journalctl -ul docker </del> <ins> journalctl -u docker </ins> ``` ## Pods in `RunContainerError`, `CrashLoopBackOff` or `Error` state

Related discussion:
text: 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: Documentation contains an error: URL: chapter: kubeadm blocks when removing managed containers: Text in doc: Inspecting the logs for docker may also be useful: Error: This command runs into an error (on my ubuntu 18.04 distribution): Proposed Solution: Replace command with: Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version: v1.18--<!--Additional Information:--
/sig cluster-lifecycle /good-first-issue /help /kind bug it should have been or just let's go with:
This request has been marked as suitable for new contributors. 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 : /sig cluster-lifecycle /good-first-issue /help /kind 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
/assign
Code change:
The Kubernetes DNS server is the only way to access `ExternalName` Services. You can find more information about `ExternalName` resolution in <del> [DNS Pods and Services](/docs/concepts/services-networking/dns-pod-service/). </del> <ins> [DNS for Services and Pods](/docs/concepts/services-networking/dns-pod-service/). </ins> ## Headless Services

Related discussion:
text: A link reference from to has the title text whereas the current title of that page is It will be a little less confusing if the link title was adjusted to be the same as the page title.
/sig docs /language en /assign
The label(s) cannot be applied, because the repository doesn't have them. <detailsIn response to : /kind suggestion I Agree on your point. If triage accepted, i will update this reference text from to that can avoid confusion. 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 Agree on your point. If triage accepted, i will update this reference text from to that can avoid confusion.
This issue got resolved with PR .
/triage accepted
Code change:
You can use {{< glossary_tooltip term_id="containerd" text="ContainerD" >}} 1.4.0+ as the container runtime for Kubernetes nodes that run Windows. <del> Learn how to [install ContainerD on a Windows node](/docs/setup/production-environment/container-runtimes/#install-containerd). </del> <ins> Learn how to [install ContainerD on a Windows node](/docs/setup/production-environment/container-runtimes/#containerd). </ins> {{< note >}} There is a [known limitation](/docs/tasks/configure-pod-container/configure-gmsa/#gmsa-limitations) when using GMSA with containerd to access Windows network shares, which requires a

Related discussion:
text: This is a Bug Report Problem: The link for in  is incorrect. It is redirecting to but it should redirect to Proposed Solution: should redirect to instead of
/sig docs /kind bug
Page related to the issue:
/language en
I would to like to solve this issue if triage gets accepted.
/triage accepted
/assign
The issue is fixed here:
Code change:
{{% /tab %}} {{< /tabs >}} <ins> The preceding commands don't remove images, containers, volumes, or customized configuration files on your host. To delete them, follow Docker's instructions to [Uninstall Docker Engine](https://docs.docker.com/engine/install/ubuntu/#uninstall-docker-engine). {{< caution >}} Docker's instructions for uninstalling Docker Engine create a risk of deleting containerd. Be careful when executing commands. {{< /caution >}} </ins>

Related discussion:
text: As part of "Remove Docker Engine", this page should probably also tell the user that may want to clean up space was consumed by docker, e.g. . Otherwise, potentially much space is left used but unmanaged on the node.
Sounds good. We could link to and similar page fragments; if we do, we should caution people that Docker's advice has a risk of trampling on containerd. Ideally, we provide just links to third party docs here. However, neither Docker Engine nor containerd has docs for migrating from one thing to the other (let alone any Kubernetes-specific considerations). I'm happy to treat that as a valid exception from the usual .
/sig node /triage accepted /language en /priority backlog
/assign
Code change:
- Subject-matching properties: - `user`, type string; the user-string from `--token-auth-file`. If you specify `user`, it must match the username of the authenticated user. - `group`, type string; if you specify `group`, it must match one of the groups of the authenticated user. `system:authenticated` matches all authenticated requests. `system:unauthenticated` matches all unauthenticated requests. <del> - `readonly`, type boolean, when true, means that the policy only applies to get, list, and watch operations. </del> - Resource-matching properties: <del> - `apiGroup`, type string; an API group, such as `extensions`. `*` matches all API groups. - `namespace`, type string; a namespace string. `*` matches all resource requests. - `resource`, type string; a resource, such as `pods`. `*` matches all resource requests. </del> <ins> - `apiGroup`, type string; an API group. - Ex: `extensions` - Wildard: `*` matches all API groups. - `namespace`, type string; a namespace. - Ex: `kube-system` - Wildard: `*` matches all resource requests. - `resource`, type string; a resource type - Ex: `pods` - Wildcard: `*` matches all resource requests. </ins> - Non-resource-matching properties: <del> - `nonResourcePath`, type string; matches the non-resource request paths (like `/version` and `/apis`). `*` matches all non-resource requests. `/foo/*` matches `/foo/` and all of its subpaths. </del> <ins> - `nonResourcePath`, type string; non-resource request paths. - Ex: `/version` or `/apis` - Wildcard: - `*` matches all non-resource requests. - `/foo/*` matches `/foo/` and all of its subpaths. - `readonly`, type boolean, when true, means that the policy only applies to get, list, and watch operations. </ins> <del> An unset property is the same as a property set to the zero value for its type </del> <ins> **NOTES:** An unset property is the same as a property set to the zero value for its type </ins> (e.g. empty string, 0, false). However, unset should be preferred for readability.

Related discussion:
text: <!-- Thanks for filing an issue! Before submitting, please fill in the following information. --<!--Required Information--This is a... [ ] Feature Request [X] Bug Report Problem: The link "build-tools/" doesn't work anymore and returns 404. Proposed Solution: Fix the link Page to Update:
Fixed. Thanks!
Code change:
- Subject-matching properties: - `user`, type string; the user-string from `--token-auth-file`. If you specify `user`, it must match the username of the authenticated user. - `group`, type string; if you specify `group`, it must match one of the groups of the authenticated user. `system:authenticated` matches all authenticated requests. `system:unauthenticated` matches all unauthenticated requests. <del> - `readonly`, type boolean, when true, means that the policy only applies to get, list, and watch operations. </del> - Resource-matching properties: <del> - `apiGroup`, type string; an API group, such as `extensions`. `*` matches all API groups. - `namespace`, type string; a namespace string. `*` matches all resource requests. - `resource`, type string; a resource, such as `pods`. `*` matches all resource requests. </del> <ins> - `apiGroup`, type string; an API group. - Ex: `extensions` - Wildard: `*` matches all API groups. - `namespace`, type string; a namespace. - Ex: `kube-system` - Wildard: `*` matches all resource requests. - `resource`, type string; a resource type - Ex: `pods` - Wildcard: `*` matches all resource requests. </ins> - Non-resource-matching properties: <del> - `nonResourcePath`, type string; matches the non-resource request paths (like `/version` and `/apis`). `*` matches all non-resource requests. `/foo/*` matches `/foo/` and all of its subpaths. </del> <ins> - `nonResourcePath`, type string; non-resource request paths. - Ex: `/version` or `/apis` - Wildcard: - `*` matches all non-resource requests. - `/foo/*` matches `/foo/` and all of its subpaths. - `readonly`, type boolean, when true, means that the policy only applies to get, list, and watch operations. </ins> <del> An unset property is the same as a property set to the zero value for its type </del> <ins> **NOTES:** An unset property is the same as a property set to the zero value for its type </ins> (e.g. empty string, 0, false). However, unset should be preferred for readability.

Related discussion:
text: <!-- 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: Page url: in line 83, click PetSets guide occur 404 error. Proposed Solution: Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--
Fixed.
Code change:
- Subject-matching properties: - `user`, type string; the user-string from `--token-auth-file`. If you specify `user`, it must match the username of the authenticated user. - `group`, type string; if you specify `group`, it must match one of the groups of the authenticated user. `system:authenticated` matches all authenticated requests. `system:unauthenticated` matches all unauthenticated requests. <del> - `readonly`, type boolean, when true, means that the policy only applies to get, list, and watch operations. </del> - Resource-matching properties: <del> - `apiGroup`, type string; an API group, such as `extensions`. `*` matches all API groups. - `namespace`, type string; a namespace string. `*` matches all resource requests. - `resource`, type string; a resource, such as `pods`. `*` matches all resource requests. </del> <ins> - `apiGroup`, type string; an API group. - Ex: `extensions` - Wildard: `*` matches all API groups. - `namespace`, type string; a namespace. - Ex: `kube-system` - Wildard: `*` matches all resource requests. - `resource`, type string; a resource type - Ex: `pods` - Wildcard: `*` matches all resource requests. </ins> - Non-resource-matching properties: <del> - `nonResourcePath`, type string; matches the non-resource request paths (like `/version` and `/apis`). `*` matches all non-resource requests. `/foo/*` matches `/foo/` and all of its subpaths. </del> <ins> - `nonResourcePath`, type string; non-resource request paths. - Ex: `/version` or `/apis` - Wildcard: - `*` matches all non-resource requests. - `/foo/*` matches `/foo/` and all of its subpaths. - `readonly`, type boolean, when true, means that the policy only applies to get, list, and watch operations. </ins> <del> An unset property is the same as a property set to the zero value for its type </del> <ins> **NOTES:** An unset property is the same as a property set to the zero value for its type </ins> (e.g. empty string, 0, false). However, unset should be preferred for readability.

Related discussion:
text: This is a... [ ] Feature Request [X] Bug Report Problem: link "Minikube installation guide" points to which is 404 Proposed Solution: fix the link by making it absolute: Page to Update:
Fixed.
Code change:
- Subject-matching properties: - `user`, type string; the user-string from `--token-auth-file`. If you specify `user`, it must match the username of the authenticated user. - `group`, type string; if you specify `group`, it must match one of the groups of the authenticated user. `system:authenticated` matches all authenticated requests. `system:unauthenticated` matches all unauthenticated requests. <del> - `readonly`, type boolean, when true, means that the policy only applies to get, list, and watch operations. </del> - Resource-matching properties: <del> - `apiGroup`, type string; an API group, such as `extensions`. `*` matches all API groups. - `namespace`, type string; a namespace string. `*` matches all resource requests. - `resource`, type string; a resource, such as `pods`. `*` matches all resource requests. </del> <ins> - `apiGroup`, type string; an API group. - Ex: `extensions` - Wildard: `*` matches all API groups. - `namespace`, type string; a namespace. - Ex: `kube-system` - Wildard: `*` matches all resource requests. - `resource`, type string; a resource type - Ex: `pods` - Wildcard: `*` matches all resource requests. </ins> - Non-resource-matching properties: <del> - `nonResourcePath`, type string; matches the non-resource request paths (like `/version` and `/apis`). `*` matches all non-resource requests. `/foo/*` matches `/foo/` and all of its subpaths. </del> <ins> - `nonResourcePath`, type string; non-resource request paths. - Ex: `/version` or `/apis` - Wildcard: - `*` matches all non-resource requests. - `/foo/*` matches `/foo/` and all of its subpaths. - `readonly`, type boolean, when true, means that the policy only applies to get, list, and watch operations. </ins> <del> An unset property is the same as a property set to the zero value for its type </del> <ins> **NOTES:** An unset property is the same as a property set to the zero value for its type </ins> (e.g. empty string, 0, false). However, unset should be preferred for readability.

Related discussion:
text: <!-- 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: Multiple links on the page generate 404 Not Found Examples: (redirected from ) (redirected from ) Proposed Solution: fix the links Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--
Here is the full list of broken links on xhyve driver kvm (driver installation) xhyve (driver installation) See DRIVERS docker-env command minikube start minikube stop minikube delete full CLI docs
Code change:
- Subject-matching properties: - `user`, type string; the user-string from `--token-auth-file`. If you specify `user`, it must match the username of the authenticated user. - `group`, type string; if you specify `group`, it must match one of the groups of the authenticated user. `system:authenticated` matches all authenticated requests. `system:unauthenticated` matches all unauthenticated requests. <del> - `readonly`, type boolean, when true, means that the policy only applies to get, list, and watch operations. </del> - Resource-matching properties: <del> - `apiGroup`, type string; an API group, such as `extensions`. `*` matches all API groups. - `namespace`, type string; a namespace string. `*` matches all resource requests. - `resource`, type string; a resource, such as `pods`. `*` matches all resource requests. </del> <ins> - `apiGroup`, type string; an API group. - Ex: `extensions` - Wildard: `*` matches all API groups. - `namespace`, type string; a namespace. - Ex: `kube-system` - Wildard: `*` matches all resource requests. - `resource`, type string; a resource type - Ex: `pods` - Wildcard: `*` matches all resource requests. </ins> - Non-resource-matching properties: <del> - `nonResourcePath`, type string; matches the non-resource request paths (like `/version` and `/apis`). `*` matches all non-resource requests. `/foo/*` matches `/foo/` and all of its subpaths. </del> <ins> - `nonResourcePath`, type string; non-resource request paths. - Ex: `/version` or `/apis` - Wildcard: - `*` matches all non-resource requests. - `/foo/*` matches `/foo/` and all of its subpaths. - `readonly`, type boolean, when true, means that the policy only applies to get, list, and watch operations. </ins> <del> An unset property is the same as a property set to the zero value for its type </del> <ins> **NOTES:** An unset property is the same as a property set to the zero value for its type </ins> (e.g. empty string, 0, false). However, unset should be preferred for readability.

Related discussion:
text: I wish /docs/user-guide/horizontal-pod-autoscaling/walkthrough/ actually contained the information, or at least a link to autoscaling by custom application logic (as referred to by the first sentence in the article - . The second half of this article seems like the correct target link -
Fixed. Thanks.