jiebi/CodeConvo huggingface dataset:
Code change:
{{% tab name="Windows (PowerShell)" %}} <!-- <del> Start a Powershell session, set `$Version` to the desired version (ex: `$Version=1.4.3`), and then run the following commands: </del> <ins> Start a Powershell session, set `$Version` to the desired version (ex: `$Version=1.4.3`), and then run the following commands: </ins> --> <del> 启动 Powershell 会话，将 `$Version` 设置为所需的版本（例如：`$ Version=1.4.3`）， </del> <ins> 启动 Powershell 会话，将 `$Version` 设置为所需的版本（例如：`$Version=1.4.3`）， </ins> 然后运行以下命令： <!--

Related discussion:
text: ! w sudo systemctl enable crio --now
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
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: Typo in zh/docs/setup/production-environment/container-runtimes Proposed Solution: -Page to Update: zh: (en: ) <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--/retitle [zh] Typo in docs/setup/production-environment/container-runtimes /kind bug /language zh
Page is a little bit lagging behind. Will fix. /assign
Code change:
1. Create `example-ingress.yaml` from the following file: <del> ```yaml apiVersion: networking.k8s.io/v1 kind: Ingress metadata: name: example-ingress annotations: nginx.ingress.kubernetes.io/rewrite-target: /$1 spec: rules: - host: hello-world.info http: paths: - path: / pathType: Prefix backend: service: name: web port: number: 8080 ``` </del> <ins> {{< codenew file="ingress/example-ingress.yaml" >}} </ins> 1. Create the Ingress resource by running the following command: ```shell <del> kubectl apply -f example-ingress.yaml </del> <ins> kubectl apply -f https://k8s.io/examples/ingress/example-ingress.yaml </ins> ``` Output:

Related discussion:
text: This is a Bug Report Problem: it seems that there is wrong indentation example- Proposed Solution: change to: path: / backend: serviceName: web servicePort: 8080 instead of: path: / backend: serviceName: web servicePort: 8080 Page to Update: Additional Information: This is the error thrown: $ kubectl apply -f example- error: error validating "example-": error validating data: [ValidationError([0]): unknown field "backend" in , ValidationError([0][0]): missing required field "backend" in ]; if you choose to ignorethese errors, turn validation off with --validate=false $
Thank you for your submission and have tried to fix it. /kind bug /language en /assign
Code change:
what that means, check out the blog post [Don't Panic: Kubernetes and Docker](/blog/2020/12/02/dont-panic-kubernetes-and-docker/). <ins> Also, you can read [check whether Dockershim deprecation affects you](/docs/tasks/administer-cluster/migrating-from-dockershim/check-if-dockershim-deprecation-affects-you/) to check whether it does. </ins> ### Why is dockershim being deprecated? Maintaining dockershim has become a heavy burden on the Kubernetes maintainers.

Related discussion:
text: cc: Task docs referencing how to check if dockershim removal affects users to be to the discussions. Link to be : (/docs/tasks/administer-cluster/migrating-from-dockershim/check-if-dockershim-deprecation-affects-you/)
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
Issue raised per
/sig docs /language en
Code change:
The output displays 0 in the DESIRED and CURRENT columns: <del> NAME                                 DESIRED   CURRENT   READY   AGE </del> <ins> NAME                                  DESIRED   CURRENT   READY   AGE </ins> ... <del> dns-autoscaler-6b59789fc8            0         0         0       ... </del> <ins> kube-dns-autoscaler-6b59789fc8        0         0         0       ... </ins> ... <del> ### Option 2: Delete the dns-autoscaler deployment </del> <ins> ### Option 2: Delete the kube-dns-autoscaler deployment </ins> <del> This option works if dns-autoscaler is under your own control, which means </del> <ins> This option works if kube-dns-autoscaler is under your own control, which means </ins> no one will re-create it: ```shell <del> kubectl delete deployment dns-autoscaler --namespace=kube-system </del> <ins> kubectl delete deployment kube-dns-autoscaler --namespace=kube-system </ins> ``` The output is: <del> deployment.apps "dns-autoscaler" deleted </del> <ins> deployment.apps "kube-dns-autoscaler" deleted </ins> <del> ### Option 3: Delete the dns-autoscaler manifest file from the master node </del> <ins> ### Option 3: Delete the kube-dns-autoscaler manifest file from the master node </ins> <del> This option works if dns-autoscaler is under control of the (deprecated) </del> <ins> This option works if kube-dns-autoscaler is under control of the (deprecated) </ins> [Addon Manager](https://git.k8s.io/kubernetes/cluster/addons/README.md), and you have write access to the master node. Sign in to the master node and delete the corresponding manifest file. <del> The common path for this dns-autoscaler is: </del> <ins> The common path for this kube-dns-autoscaler is: </ins> /etc/kubernetes/addons/dns-horizontal-autoscaler/dns-horizontal-autoscaler.yaml After the manifest file is deleted, the Addon Manager will delete the <del> dns-autoscaler Deployment. </del> <ins> kube-dns-autoscaler Deployment. </ins>

Related discussion:
text: dns-horizontal- kube-dns-autoscaler dns-autoscaler 2
/language zh
please describe the issue in English
page related to the issue:
/triage needs-information
Translate to English: The kube-dns-autoscaler used in dns-horizontal- and the dns-autoscaler used in subsequent commands are confused and out of sync. It seems that the English version also has this problem. /triage accepted /kind bug /retitle Inconsistent name in the DNS horizontal autoscaling example
/language en
/assign
Code change:
このリポジトリには、[KubernetesのWebサイトとドキュメント](https://kubernetes.io/)をビルドするために必要な全アセットが格納されています。貢献に興味を持っていただきありがとうございます！ <ins> - [ドキュメントに貢献する](#contributing-to-the-docs) - [翻訳された`README.md`一覧](#localization-readmemds) </ins> # リポジトリの使い方 Hugo(Extended version)を使用してWebサイトをローカルで実行することも、コンテナランタイムで実行することもできます。コンテナランタイムを使用することを強くお勧めします。これにより、本番Webサイトとのデプロイメントの一貫性が得られます。

Related discussion:
text: This is a Feature Request What would you like to be Update README- Why is this needed has been updated after translated Comments /language ja
/triage accepted
Code change:
`zk-1` is scheduled. ```shell <del> kubectl drain $(kubectl get pod zk-1 --template {{.spec.nodeName}}) --ignore-daemonsets --force --delete-local-data "kubernetes-node-ixsl" cordoned </del> <ins> kubectl drain $(kubectl get pod zk-1 --template {{.spec.nodeName}}) --ignore-daemonsets --force --delete-emptydir-data "kubernetes-node-ixsl" cordoned </ins> ``` ```

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: Flag --delete-local-data has been deprecated, This option is deprecated and will be deleted. Use --delete-emptydir-data. I don’t know if it’s a good time to update this flag . If so, I can help update it. Proposed Solution: Update to Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--/sig cluster-lifecycle
cc
i see the discussion / PR here: using in the kubeadm docs makes sense. /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 : Flag --delete-local-data has been deprecated, This option is deprecated and will be deleted. Use --delete-emptydir-data. I don’t know if it’s a good time to update this flag . If so, I can help update it. /help </details
/assign
Code change:
check the documentation for that version. {{< /note >}} <!-- body --> ## Install and configure prerequisites <del> The following steps apply common settings for Kubernetes nodes on Linux. </del> <ins> The following steps apply common settings for Kubernetes nodes on Linux. </ins> You can skip a particular setting if you're certain you don't need it. <del> For more information, see [Network Plugin Requirements](/docs/concepts/extend-kubernetes/compute-storage-net/network-plugins/#network-plugin-requirements) or the documentation for your specific container runtime. </del> <ins> For more information, see [Network Plugin Requirements](/docs/concepts/extend-kubernetes/compute-storage-net/network-plugins/#network-plugin-requirements) or the documentation for your specific container runtime. </ins> ### Forwarding IPv4 and letting iptables see bridged traffic

Related discussion:
text: This section: I would add information like here: Note: In v1.22, if the user is not setting the cgroupDriver field under KubeletConfiguration, kubeadm will default it to systemd.
this section: already links to: PRs welcome with proposed improvements. /help /sig cluster-lifecycle
If someone wants to help here, I'm not sure what steps they should follow to assist. Because of that: /remove-help
/language en
I think the suggestion is to add something about to container-runtimes pages but I don't think that fits well on that page because it only covers the container runtime side. What could be though is that there's a note/reminder to ensure they are always the same. I can work on that if we agree what's what we want here.
hmm, looks like this is already covered too.
some additional feedback in
/triage accepted
The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs. This bot triages issues and PRs according to the following rules: After 90d of inactivity, is applied After 30d of inactivity since was applied, is applied After 30d of inactivity since was applied, the issue is closed You can: Mark this issue or PR as fresh with Mark this issue or PR as rotten with Close this issue or PR with Offer to help out with [Issue Triage][1] Please send feedback to sig-contributor-experience at . /lifecycle stale [1]:
/assign
Code change:
The value for this annotation must be **true** to take effect. This annotation indicates that pods running as this service account may only reference Secret API objects specified in the service account's `secrets` field. <ins> ### node.kubernetes.io/exclude-from-external-load-balancer Example: `node.kubernetes.io/exclude-from-external-load-balancer` Used on: Node Kubernetes automatically enables the `ServiceNodeExclusion` feature gate on the clusters it creates. With this feature gate enabled on a cluster, you can add labels to particular worker nodes to exclude them from the list of backend servers. The following command can be used to exclude a worker node from the list of backend servers in a backend set- `kubectl label nodes <node-name> node.kubernetes.io/exclude-from-external-load-balancers=true` </ins> ### controller.kubernetes.io/pod-deletion-cost {#pod-deletion-cost} Example: `controller.kubernetes.io/pod-deletion-cost: "10"`

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: I have a node in Minikube that's labelled with the key . This looks intended, but doesn't document that label. Proposed Solution: Document that label; as a side effect, this registers it. I can guess what this label does but I don't actually know. If you pick this issue up, part of your task is to find out that detail. Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--Additional Information: /sig node /language en /priority backlog PS. If this label isn't supposed to be used any more, we should also mark it as deprecated.
/triage accepted
/assign
Code change:
| Scala                | [github.com/hagay3/skuber](https://github.com/hagay3/skuber) | | Scala                | [github.com/joan38/kubernetes-client](https://github.com/joan38/kubernetes-client) | | Swift                | [github.com/swiftkube/client](https://github.com/swiftkube/client) | <del> | DotNet               | [github.com/tonnyeremin/kubernetes_gen](https://github.com/tonnyeremin/kubernetes_gen) | | DotNet (RestSharp)   | [github.com/masroorhasan/Kubernetes.DotNet](https://github.com/masroorhasan/Kubernetes.DotNet) | | Elixir               | [github.com/obmarg/kazan](https://github.com/obmarg/kazan/) | | Elixir               | [github.com/coryodaniel/k8s](https://github.com/coryodaniel/k8s) | </del>

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: Client Libraries lists 3rd party software. Kubernetes docs allow content for third-party projects only when: Content documents software in the Kubernetes project Content documents software that’s out of project but necessary for Kubernetes to function Content is canonical on , or links to canonical content elsewhere Proposed Solution: ~Remove links to 3rd party client libraries~ Sort list alphabetically Page to Update: Additional Information: Part of umbrella issue /language en
There was some discussion in about this. What was the outcome?
This is also relevant to
We discussed this in the 2020-06-23 SIG Docs weekly meeting. proposed flagging the third party client libraries with an cautionary note about quality. recommended ensuring that all client projects within are linked to notes that this is strictly content as outside what's allowed in the but that it is useful to a wide user base also points out that client libraries in general (whether in-project or otherwise) are useful to make Kubernetes work as you want it to? This content is unique (there's not a good alternative page elsewhere on the web). What's important is to identifying an owning SIG and having some means to keep the list live and relevant. Removal is held until the end of the v1.19 release cycle, so positive discussion before that date is helpful and I encourage it. /sig community /sig api-machinery we are conflicted about where to put this; we're not sure it fits inside documentation any more - would SIG Community be interested in hosting this list? what are your views on this list, in light of
The label(s) cannot be applied, because the repository doesn't have them <detailsIn response to : We discussed this in the 2020-06-23 SIG Docs weekly meeting. proposed flagging the third party client libraries with an cautionary note about quality. recommended ensuring that all client projects within are linked to notes that this is strictly content as outside what's allowed in the but that it is useful to a wide user base also points out that client libraries in general (whether in-project or otherwise) are useful to make Kubernetes work as you want it to?
Code change:
| Scala                | [github.com/hagay3/skuber](https://github.com/hagay3/skuber) | | Scala                | [github.com/joan38/kubernetes-client](https://github.com/joan38/kubernetes-client) | | Swift                | [github.com/swiftkube/client](https://github.com/swiftkube/client) | <del> | DotNet               | [github.com/tonnyeremin/kubernetes_gen](https://github.com/tonnyeremin/kubernetes_gen) | | DotNet (RestSharp)   | [github.com/masroorhasan/Kubernetes.DotNet](https://github.com/masroorhasan/Kubernetes.DotNet) | | Elixir               | [github.com/obmarg/kazan](https://github.com/obmarg/kazan/) | | Elixir               | [github.com/coryodaniel/k8s](https://github.com/coryodaniel/k8s) | </del>

Related discussion:
text: /sig api-machinery we are conflicted about where to put this; we're not sure it fits inside documentation any more - would SIG Community be interested in hosting this list? what are your views on this list, in light of 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
Raised visibility in
sadly some projects under the org is not actively maintained. those libraries (go/java/python/dotnet/js) already linked are fairly active. can we consider to append a new link for C/C++ which is newly & active months ago? i wonder if the community-maintained list is stale b/c it seems rarely updated. also i noticed there's a number of repos stopped maintaining for 1-2 years or even longer period of time: am slighting leaning on keeping the community list as most of these projects are driven by individuals instead of dedicated vendors -- the more we have the better?
Should this issue remain open? Thanks!
I can see one thing that still needs doing /retitle Sort third party client library links so the link text is clearly in alphabetical order. Order by language then by URI.
Issues go stale after 90d of inactivity. Mark the issue as fresh with . Stale issues rot after an additional 30d of inactivity and eventually close. If this issue is safe to close now please do so with . Send feedback to sig-testing, kubernetes/test-infra and/or . /lifecycle stale
/remove-lifecycle stale
The remaining sorting is straightforward; if it weren't for the issue history I'd say it's a good first issue. /help /kind cleanup
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 : The remaining sorting is straightforward; if it weren't for the issue history I'd say it's a good first issue. /help /kind cleanup 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
Code change:
## Letting iptables see bridged traffic <ins> Make sure that the `br_netfilter` module is loaded. This can be done by running `lsmod | grep br_netfilter`. To load it explicitly call `sudo modprobe br_netfilter`. </ins> As a requirement for your Linux Node's iptables to correctly see bridged traffic, you should ensure `net.bridge.bridge-nf-call-iptables` is set to 1 in your `sysctl` config, e.g. ```bash

Related discussion:
text: This paragraph is a bit backwards. It would be more intuitive to start with the "Make sure that the br_netfilter module is loaded before this step..." phrases.
/language en /kind cleanup /priority backlog /good-first-issue Thanks
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 : /language en /kind cleanup /priority backlog /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
/sig cluster-lifecycle
Code change:
<div class="row"> <div class="col-md-8"> <p><b>The Master is responsible for managing the cluster.</b> The master coordinates all activities in your cluster, such as scheduling applications, maintaining applications' desired state, scaling applications, and rolling out new updates.</p> <del> <p><b>A node is a VM or a physical computer that serves as a worker machine in a Kubernetes cluster.</b> Each node has a Kubelet, which is an agent for managing the node and communicating with the Kubernetes master. The node should also have tools for handling container operations, such as <a href="https://www.docker.com/">Docker</a> or <a href="https://coreos.com/rkt/">rtk</a>. A Kubernetes cluster that handles production traffic should have a minimum of three nodes.</p> </del> <ins> <p><b>A node is a VM or a physical computer that serves as a worker machine in a Kubernetes cluster.</b> Each node has a Kubelet, which is an agent for managing the node and communicating with the Kubernetes master. The node should also have tools for handling container operations, such as <a href="https://www.docker.com/">Docker</a> or <a href="https://coreos.com/rkt/">rkt</a>. A Kubernetes cluster that handles production traffic should have a minimum of three nodes.</p> </ins> </div> <div class="col-md-4">

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:
<div class="row"> <div class="col-md-8"> <p><b>The Master is responsible for managing the cluster.</b> The master coordinates all activities in your cluster, such as scheduling applications, maintaining applications' desired state, scaling applications, and rolling out new updates.</p> <del> <p><b>A node is a VM or a physical computer that serves as a worker machine in a Kubernetes cluster.</b> Each node has a Kubelet, which is an agent for managing the node and communicating with the Kubernetes master. The node should also have tools for handling container operations, such as <a href="https://www.docker.com/">Docker</a> or <a href="https://coreos.com/rkt/">rtk</a>. A Kubernetes cluster that handles production traffic should have a minimum of three nodes.</p> </del> <ins> <p><b>A node is a VM or a physical computer that serves as a worker machine in a Kubernetes cluster.</b> Each node has a Kubelet, which is an agent for managing the node and communicating with the Kubernetes master. The node should also have tools for handling container operations, such as <a href="https://www.docker.com/">Docker</a> or <a href="https://coreos.com/rkt/">rkt</a>. A Kubernetes cluster that handles production traffic should have a minimum of three nodes.</p> </ins> </div> <div class="col-md-4">

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.