jiebi/CodeConvo huggingface dataset:
Code change:
In general, Pods remain until a human or {{< glossary_tooltip term_id="controller" text="controller" >}} process explicitly removes them. <del> The control plane cleans up terminated Pods (with a phase of `Succeeded` or </del> <ins> The control plane cleans up terminated Pods (with a phase of `Succeeded` or </ins> `Failed`), when the number of Pods exceeds the configured threshold (determined by `terminated-pod-gc-threshold` in the kube-controller-manager). This avoids a resource leak as Pods are created and terminated over time.

Related discussion:
text: This is a Bug Report <!--Required Information--Problem: The page has a section. This section contains link to a Handler documentation. This link does not work: Proposed Solution: Update the link to the handler documentation on the page in the section of the page. Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--
/kind bug /language en
/assign I'm going to fix the link to the correct one.
Code change:
Install and configure prerequisites: ```shell <ins> # Create the .conf file to load the modules at bootup cat <<EOF | sudo tee /etc/modules-load.d/crio.conf overlay br_netfilter EOF </ins> sudo modprobe overlay sudo modprobe br_netfilter

Related discussion:
text: Problem: The documentation references loading the overlay and brnetfilter kernel modules at both of these locations: Modules do not persist reboots Documentation states that they will persist across reboots. Cluster will fail pre-flight if modules are not loaded Proposed Solution: In installation prerequisites add: cat <<EOF | sudo tee /etc/modules- overlay brnetfilter EOF This is correct in the containerd installation prerequisites but appears missing from CRI-O. Modules do not appear to persist across reboots unless /etc/modules-load.d has a config reference to load at boot. In the example given at add: cat <<EOF | sudo tee /etc/modules- br_netfilter EOF
a PR with the fix is welcome. /sig node cluster-lifecycle /triage accepted
Thank you PRs submitted.
please close this once the PRs merge. or add in one of the PR descriptions.
Code change:
other = "suggest an improvement" [layouts_docs_partials_feedback_issue] <del> other = "Open an issue in the GitHub repo if you want to " </del> <ins> other = """Open an issue in the [GitHub Repository](https://www.github.com/kubernetes/website/) if you want to """ </ins> [layouts_docs_partials_feedback_or] other = "or"

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 <!-- Describe as precisely as possible how this feature/enhancement should work from the user perspective. What should be changed, etc. --I want to add a hyperlink to the "GitHub repo". ! Comments <!-- Any additional related comments that might help. Drawings/mockups would be extremely helpful (if required). --Link to be :
/sig docs
/language en /triage needs-information
Hi Could you please describe on which page of the documentation you are facing issue?
This is under the feedback section of too many pages. We have to change all of them.
I think we need not change much here, A slight change in i18n markdown should do the trick
/assign I'll do that
/remove-triage needs-information
Thanks for raising the PR . Also, Please focus on those issues first which have label.
/triage accepted /priority backlog
Code change:
* GCEPersistentDisk * AWSElasticBlockStore <ins> * AzureFile * FC (Fibre Channel) </ins> * NFS * iSCSI * RBD (Ceph Block Device) <ins> * CephFS * Cinder (OpenStack block storage) </ins> * Glusterfs <ins> * VsphereVolume </ins> * HostPath (single node testing only -- local storage is not supported in any way and WILL NOT WORK in a multi-node cluster)

Related discussion:
text: This is a... <!-- choose one by changing [ ] to [x] --- [ ] Feature Request [X] Bug Report Problem: The command to create the sock-shop application error out (it's also not necessary to create the namespace beforehand as that is already define in ): Proposed Solution: Change the command to: Page to Update: Kubernetes Version: 1.6.1
I think this is an issue that needs to be fixed in socks shop.
This merged PR should resolve the issue
Code change:
```shell sudo apt-get update <del> sudo apt-get install -y apt-transport-https ca-certificates curl </del> <ins> sudo apt-get install -y ca-certificates curl </ins> ``` <ins> {{< note >}} If you use Debian 9 (stretch) or earlier you would also need to install `apt-transport-https`: ```shell sudo apt-get install -y apt-transport-https ``` {{< /note >}} </ins> 2. Download the Google Cloud public signing key: ```shell

Related discussion:
text: Hi, apt-transport-https is a dummy package since apt 1.5, means it's not needed anymore as of Debian 10 and Ubuntu 18.04.
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 Linux kubectl package install instructions recommend dummy package This issue is about /kind cleanup /language en The fix would be to omit mentioning , provided that we are confident that all readers are using at least Debian 10. I think the Ubuntu side of things we can take for granted. /priority awaiting-more-evidence
We can also rather add a piece of text, something like: sh sudo apt-get install -y apt-transport-https '``
- would you be willing to update the issue description to incorporate the idea from ?
I have this PR raised. I hope that helps.
/assign
Sorry, didn't see this earlier. However, looks like already did exactly this in .
Code change:
hostNetwork: true containers: - name: konnectivity-server-container <del> image: us.gcr.io/k8s-artifacts-prod/kas-network-proxy/proxy-server:v0.0.16 </del> <ins> image: registry.k8s.io/kas-network-proxy/proxy-server:v0.0.32 </ins> command: ["/proxy-server"] args: [ "--logtostderr=true",

Related discussion:
text: This is a Bug Report Problem: The current documentation is still referring to the non-official Kubernetes container image repository introduced starting from v1.25 () and referring to an outdated version. Proposed Solution: I can take care of the PR updating the content. 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
Code change:
<ins> apiVersion: apps/v1 kind: Deployment metadata: name: retainkeys-demo spec: selector: matchLabels: app: nginx strategy: rollingUpdate: maxSurge: 30% template: metadata: labels: app: nginx spec: containers: - name: retainkeys-demo-ctr image: nginx </ins>

Related discussion:
text: This is a Feature Request What would you like to be Localize to Spanish Why is this needed There is no Spanish localization for this file. Comments /triage accepted /kind feature /language es /sig docs /area localization
/assign
/unassign
Code change:
#### Terminating <del> {{< feature-state for_k8s_version="v1.20" state="alpha" >}} </del> <ins> {{< feature-state for_k8s_version="v1.22" state="beta" >}} </ins> `Terminating` is a condition that indicates whether an endpoint is terminating. For pods, this is any pod that has a deletion timestamp set.

Related discussion:
text: This is a Bug Report <!--Required Information--The FEATURE STATE for and is mentioned under which is wrong, As per mention in the the correct Feature state for is . Proposed Solution: Update the Feature State of Serving and Terminating from to . Page to Update: <!--Additional Information:--EndpointSliceTerminatingCondition: Enables EndpointSlice and condition fields.
/assign
Fixed it here:
/language en /triage accepted
Code change:
$ kubectl get services --sort-by=.metadata.name # List pods Sorted by Restart Count <del> $ kubectl get pods --sort-by=.status.containerStatuses[0].restartCount </del> <ins> $ kubectl get pods --sort-by='.status.containerStatuses[0].restartCount' </ins> # Get the version label of all pods with label app=cassandra $ kubectl get pods --selector=app=cassandra rc -o 'jsonpath={.items[*].metadata.labels.version}'

Related discussion:
text: Does not run under as defined in the docs. This is the fix: I think wanted me to do one work on the cheat anyways ... Just leaving this here for now.
Code change:
<th class="metric_help">Help</th> <th class="metric_labels">Labels</th> <th class="metric_const_labels">Const Labels</th> <del> <th class="metric_deprecated_version">Deprecated Version</th> </del> </tr> </thead> <tbody>

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: documents metrics for Kubernetes v1.26 but that's incorrect because at the time I'm filing this the live documentation is for Kubernetes v1.25 Proposed Solution: Revert whichever PR bumped the document too early or do a careful partial revert that only omits the v1.26 changes Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--Additional Information: /sig instrumentation /language en If v1.26 gets released before we fix this, it's OK to close the issue. Consider a backport to the v1.25 docs, though.
/assign
/triage accepted
/assign
Code change:
#### Manually provisioning a Regional PD PersistentVolume Dynamic provisioning is possible using a <del> [StorageClass for GCE PD](/docs/concepts/storage/storage-classes/#gce). </del> <ins> [StorageClass for GCE PD](/docs/concepts/storage/storage-classes/#gce-pd). </ins> Before creating a PersistentVolume, you must create the persistent disk: ```shell

Related discussion:
text: Problem: The text on is not working, it should point to these Check the page for the problem. Page to Update: Proposed Solution: It should resolve this issue by adding a simple link and enhancing the document line. Update the link on the text StorageClass for GCE PD to and not to this . /kind document /assign /language en
The label(s) cannot be applied, because the repository doesn't have them. <detailsIn response to : Problem: The text on is not working, it should point to these Check the page for the problem. It should resolve this issue by adding a simple link and enhancing the document line. Update the link on the text StorageClass for GCE PD to and not to this . /assign /language en Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details
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:
``` {{% note %}} <del> ページのweightについては、1、2、3…などの値を使用せず、10、20、30…のように一定の間隔を空けた方が賢明です。こうすることで、後で別のページを間に挿入できるようになります。 </del> <ins> ページのweightについては、1、2、3…などの値を使用せず、10、20、30…のように一定の間隔を空けた方が賢明です。こうすることで、後で別のページを間に挿入できるようになります。さらに、同じディレクトリ(セクション)内の各ページのweightは、重複しないようにする必要があります。これにより、特にローカライズされたコンテンツでは、コンテンツが常に正しく整列されるようになります。 </ins> {{% /note %}} ### ドキュメントのメインメニュー

Related discussion:
text: This is a Feature Request What would you like to be We need to update /content/ja/docs/contribute/style/content- according to the English text, because it is outdated. Why is this needed /content/ja/docs/contribute/style/content- is outdated. In the English page, a note for localication was in . It needs to be to the Japanese page. Comments /language ja /assign
This issue is currently awaiting triage. SIG Docs takes a lead on issue triage for this website, but any Kubernetes member can accept issues by applying the label. The label can be by org members by writing in a comment. <detailsInstructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details
Related Issue : ,
Code change:
* Run etcd as a cluster of odd members. <del> * etcd is a leader-based distributed system. Ensure that the leader periodically send heartbeats on time to all followers to keep the cluster stable. </del> <ins> * etcd is a leader-based distributed system. Ensure that the leader periodically send heartbeats on time to all followers to keep the cluster stable. </ins> * Ensure that no resource starvation occurs. <del> Performance and stability of the cluster is sensitive to network and disk IO. Any resource starvation can lead to heartbeat timeout, causing instability of the cluster. An unstable etcd indicates that no leader is elected. Under such circumstances, a cluster cannot make any changes to its current state, which implies no new pods can be scheduled. </del> <ins> Performance and stability of the cluster is sensitive to network and disk I/O. Any resource starvation can lead to heartbeat timeout, causing instability of the cluster. An unstable etcd indicates that no leader is elected. Under such circumstances, a cluster cannot make any changes to its current state, which implies no new pods can be scheduled. </ins> <del> * Keeping stable etcd clusters is critical to the stability of Kubernetes clusters. Therefore, run etcd clusters on dedicated machines or isolated environments for [guaranteed resource requirements](https://github.com/coreos/etcd/blob/master/Documentation/op-guide/hardware.md#hardware-recommendations). </del> <ins> * Keeping etcd clusters stable is critical to the stability of Kubernetes clusters. Therefore, run etcd clusters on dedicated machines or isolated environments for [guaranteed resource requirements](https://etcd.io/docs/current/op-guide/hardware/). </ins> * The minimum recommended version of etcd to run in production is `3.2.10+`. -->

Related discussion:
text: " etcd "client.cert " etcd etcd " " etcd client.key etcd "
~ GitHub is not the right place for support requests.~ ~If you're looking for help, oyu could ask on .~ ~You can also post your question on the or the forum. There are other support venues with contributions from the wider community of Kubernetes users.~
/triage accepted /kind bug
/remove-kind support
Thanks
/language zh
/priority backlog
Code change:
/api-ref/     https://github.com/kubernetes/kubernetes/milestones/ 301 /concepts/containers/container-lifecycle-hooks/     /docs/concepts/containers/container-lifecycle-hooks/ 301 /docs/     /docs/home/ 301 <del> /docs/abstractions/controllers/petset/     /docs/concepts/workloads/controllers/statefulset/ 301 </del> /docs/admin/     /docs/concepts/cluster-administration/cluster-administration-overview/ 301 /docs/admin/add-ons/     /docs/concepts/cluster-administration/addons/ 301

Related discussion:
text: This is a... [ ] Feature Request [x] Bug Report Problem: There is a link missing that was supposed to be in section Differences between alpha PetSets and beta StatefulSets under it in the second point StatefulSet guards against split brain which ends with following text TODO: Link to doc about fencing. Change it and add the link that is required. Proposed Solution: Add link which is missing Page to Update:
PetSet has long been replaced by StatefuSet and StatefulSet has been GA'ed in 1.9. So we are going to remove this page to avoid further confusion.
Code change:
# i18n strings for the Chinese version of the site (https://kubernetes.io/zh-cn/) # 注意：修改此文件时请维持字符串名称的字母顺序并与英文版保持一致 <ins> # Avoid using conjunction_1. # Must match the context in layouts/shortcodes/release-data.html # Appears on https://kubernetes.io/releases/ # For example the "and" in "Complete 1.25 Schedule and Changelog" [conjunction_1] other = "和" </ins> [caution] other = "注意："

Related discussion:
text: What would you like to be This issue is a follow-up task from displays some English text: ! To replace this text with localized strings, you can update with from . Specifically, these:
/language zh-cn
The label(s) cannot be applied, because the repository doesn't have them. <detailsIn response to : /language zh-cn 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-docs
/language zh
/triage accepted /assign
Code change:
# Create temp directories to store files that will end up on other hosts mkdir -p /tmp/${HOST0}/ /tmp/${HOST1}/ /tmp/${HOST2}/ --> ```sh # 使用你的主机 IP 更新 HOST0、HOST1 和 HOST2 的 IP 地址 export HOST0=10.0.0.6

Related discussion:
text: apiVersion: kind: KubeletConfiguration authentication: anonymous: enabled: false webhook: enabled: false authorization: mode: AlwaysAllow apiVersion: kind: KubeletConfiguration authentication: anonymous: enabled: false webhook: enabled: false authorization: mode: AlwaysAllow
Use kubeadm to create a highly available etcd cluster apiVersion: kind: KubeletConfiguration authentication: anonymous: enabled: false webhook: enabled: false authorization: mode: AlwaysAllow There is a problem here, there is no indentation Normal should be apiVersion: kind: KubeletConfiguration authentication: anonymous: enabled: false webhook: enabled: false authorization: mode: AlwaysAllow
provide more details of the issue as it's difficult to address your issue with the information that you have provided. Atleast mention the page you are referring to. /triage needs-information
Page related to the issue :
/language zh
/retitle The YAML format may be not correct in setup-ha-etcd-with-kubeadm
/triage accepted /assign
Code change:
与 DaemonSet 中的 Pod 进行通信的几种可能模式如下： <del> - **Push**：配置 DaemonSet 中的 Pod，将更新发送到另一个服务，例如统计数据库。 </del> <ins> - **推送（Push）**：配置 DaemonSet 中的 Pod，将更新发送到另一个服务，例如统计数据库。 </ins> 这些服务没有客户端。 - **NodeIP 和已知端口**：DaemonSet 中的 Pod 可以使用 `hostPort`，从而可以通过节点 IP

Related discussion:
text: “ DaemonSet spec.template.“ “”“”
Mind propose a fix?
/triage accepted
/language zh (I presume)
The label(s) cannot be applied, because the repository doesn't have them <detailsIn response to : /language zh (I presume) 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
yes,this is chinese languge,“”change to“”
/assign
Code change:
</div> </div> <del> <div class="row"> <p>Once you've done that, move on to <a href="/docs/tutorials/kubernetes-basics/deploy-app/deploy-intro/">Using <tt>kubectl</tt> to create a Deployment</a>.</p> </div> </del> </main>

Related discussion:
text: The basic tutorial starts at , which leads to , which leads to Since one does not know what is exactly meant with in the second site, one does also the deploy step. Because it's not clearly said "" or so. Then you go back to the second site, to read all through, only to do create/expose again (with little extras), only to go back to the first site and do create/expose again. Back to the first site on step 2, pretty much at the beginning it says: But I did it already 2 times in the current tutorial flow. Now I have 3 deployments, still in the basics deployment tutorial. Its like, there are 3 tutorials to do, which are the same, but also not the same. Instead of leading the user back and forth, I suggest to do one single sufficient tutorial.
Page related to issue: /language en
/retitle Consolidate and streamline Kubernetes basics tutorials to avoid redundancy and confusion
/sig docs
the three tutorial have different purpose. What I understood the purpose of having these as three.: Yes, Its leading to back and forth of the users but I think First link showing the general functionality of the cluster's component. It Should have the link To and then link will be helpful for readers to traverse. This sequence is lacking in the page. Thats the reason why i thing its taking user back and forth several times .
There was a previous attempt at de-duplicating, but it probably has to be done again - after the removal of the Katacoda tutorials, which were using a hosted setup of to run through the tutorials "inline" with the docs
I'll change the title to frame this as a bug. /retitle Multiple, similar Kubernetes basics tutorials that cause confusion /kind bug /triage accepted /priority important-longterm
/lifecycle frozen
Yes You are right! +1
/assign
I will start working on this.
Code change:
--- linktitle: Kubernetes Documentation title: Documentation <ins> sitemap: priority: 1.0 </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 The Kubernetes website generates a sitemap. Let's highlight specific pages using priority weighting: (and any localization that copies the priority weight) (and any localization that copies the priority weight) (and any localization that copies the priority weight) Why is this needed: Making this change helps search engines understand what pages the Kubernetes project sees as important. Comments /kind feature
Code change:
ready kubernetes cluster.local in-addr.arpa ip6.arpa { pods insecure <del> upstream </del> fallthrough in-addr.arpa ip6.arpa ttl 30 } prometheus :9153 <del> proxy ./etc/resolv.conf </del> <ins> forward ./etc/resolv.conf </ins> cache 30 loop reload

Related discussion:
text: proxy --forward .
/assign /language zh
page: below yaml config comes from k8s 1.19
Code change:
kubeadm join --token <token> <master-ip>:<master-port> --discovery-token-ca-cert-hash sha256:<hash> ``` <ins> To let kubectl work in the following steps, you need to run these commands as a regular user (which is part of the output above): ``` mkdir -p $HOME/.kube sudo cp -i /etc/kubernetes/admin.conf $HOME/.kube/config sudo chown $(id -u):$(id -g) $HOME/.kube/config ``` </ins> Make a record of the `kubeadm join` command that `kubeadm init` outputs. You will need this in a moment.

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: For users using K8S versions 1.8 and lower that don't have the fix contained in it may be necessary to set for the OpenStack cloud provider when installing on OpenStack clusters that expose their Cinder endpoint using paths rather than ports to avoid auto-detection errors such as: This includes for users trying out K8S on a devstack environment, and potentially other deployment tools. In this situation it is possible to resolve using: Valid values for are: With being the default. Proposed Solution: Highlight the bs-version parameter as optional (so not minimal configuration) but required in some circumstances. Page to Update: