jiebi/CodeConvo huggingface dataset:
Change:
deb http://download.opensuse.org/repositories/devel:/kubic:/libcontainers:/stable:/cri-o:/$VERSION/$OS/ / EOF <del> curl -L https://download.opensuse.org/repositories/devel:kubic:libcontainers:stable:cri-o:$VERSION/$OS/Release.key | sudo apt-key add --keyring /etc/apt/trusted.gpg.d/libcontainers.gpg - curl -L https://download.opensuse.org/repositories/devel:/kubic:/libcontainers:/stable/$OS/Release.key | sudo apt-key add --keyring /etc/apt/trusted.gpg.d/libcontainers.gpg - </del> <ins> curl -L https://download.opensuse.org/repositories/devel:kubic:libcontainers:stable:cri-o:$VERSION/$OS/Release.key | sudo apt-key --keyring /etc/apt/trusted.gpg.d/libcontainers.gpg add - curl -L https://download.opensuse.org/repositories/devel:/kubic:/libcontainers:/stable/$OS/Release.key | sudo apt-key --keyring /etc/apt/trusted.gpg.d/libcontainers.gpg add - </ins> sudo apt-get update sudo apt-get install cri-o cri-o-runc

Discussion:
[UBUNTU 20.04] specifies the following command: This runs into the following error: Update the command to: Or... use the command which is also mentioned on the
Thanks for reporting this. I wonder if we should also recommend that readers ? /kind bug /triage accepted /priority important-longterm /language en /sig node
That is a possibility. But I think it would be logical to take over the official documentation of docker.
Did PR help here? /triage needs-information /remove-triage accepted
/retitle Incorrect commands for adding PGP keys to APT configuration
/triage accepted /remove-triage needs-information
Change:
## Cluster-level logging architectures <del> While Kubernetes does not provide a native solution for cluster-level logging, there are several common approaches you can consider. Here are some options: </del> <ins> While Kubernetes does not provide a native solution for cluster-level logging, there are several common approaches you can consider. Here are some options: </ins> * Use a node-level logging agent that runs on every node. * Include a dedicated sidecar container for logging in an application pod.

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: Url selector #kubelet-config-k8s-io-v1beta1-KubeletConfiguration doesn't make a difference between: and Proposed Solution: Removing the selector from the URLs 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
/language en
/assign
/retitle Problems with (generated) reference for kubelet configuration
Change:
For example, ```shell <del> kubectl taint nodes node1 key=value:NoSchedule </del> <ins> kubectl taint nodes node1 key1=value1:NoSchedule </ins> ``` <del> places a taint on node `node1`. The taint has key `key`, value `value`, and taint effect `NoSchedule`. </del> <ins> places a taint on node `node1`. The taint has key `key1`, value `value1`, and taint effect `NoSchedule`. </ins> This means that no pod will be able to schedule onto `node1` unless it has a matching toleration. To remove the taint added by the command above, you can run: ```shell <del> kubectl taint nodes node1 key=value:NoSchedule- </del> <ins> kubectl taint nodes node1 key1=value1:NoSchedule- </ins> ``` You specify a toleration for a pod in the PodSpec. Both of the following tolerations "match" the

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 Update to use a key of rather than , and a value of rather than . Why is this needed Some sections of Taints and Tolerations concept page suggest setting a taint where the key is called and the value is . This is confusing because when the reader sees example commands they are unsure whether represents the literal text or the example. This change will help clear up that confusion. Comments /language en /good first issue
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
It's also OK to use and rather than my suggestion of and . Whichever you prefer.
/good-first-issue
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 : /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:
kubectl port-forward deployment/mongo :27017 ``` <del> The output is similar to this: ``` Forwarding from 127.0.0.1:63753 -> 27017 Forwarding from [::1]:63753 -> 27017 ``` </del> The `kubectl` tool finds a local port number that is not in use (avoiding low ports numbers, because these might be used by other applications). The output is similar to:

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: There is a duplicate code block in . FYI: is like this: Proposed Solution: Delete one of the duplicate code block. 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
/language en
Change:
description: > A detailed look at the different policy levels defined in the Pod Security Standards. content_type: concept <del> weight: 10 </del> <ins> weight: 15 </ins> --- <!-- overview -->

Discussion:
This is a Refactor request <!-- 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: The overview page at is a bit out of date: no reference to I'm not convinced that the “Four Cs of cloud native security” model is useful for readers to learn Does not align with other CNCF documents, such as Proposed Solution: Either: remove outright migrate content from into several destinations (keep this brief but on-point) &hellip;and then redirect to Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--Additional Information: /sig docs /sig security /language en
If we keep the link to then we should update it to be as this is the English docs.
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 /triage accepted
Also see
/assign
I'd appreciate a (fresh) review on .
Change:
* Learn more about [debugging a StatefulSet](/docs/tasks/debug-application-cluster/debug-stateful-set/). * Learn more about [deleting a StatefulSet](/docs/tasks/run-application/delete-stateful-set/). * Learn more about [force deleting StatefulSet Pods](/docs/tasks/run-application/force-delete-stateful-set-pod/). <del> * Look in the [Helm Charts repository](https://github.com/kubernetes/charts) </del> <ins> * Look in the [Helm Charts repository](https://artifacthub.io/) </ins> for other stateful application examples.

Discussion:
Helm Charts repository ( ) is obsolete. This sentence should be removed or updated. might be appropriate.
If this issue is validated, may I take this up?
/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 : /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 en
/assign
Change:
#### Dockerfile ```conf <del> FROM node:0.12 </del> <ins> FROM node:4.4 </ins> EXPOSE 8080 COPY server.js . CMD node server.js ``` <del> This "recipe" for the Docker image will start from the Node 0.12 image found on the Docker registry, expose port 8080, copy our `server.js` file to the image and start the Node server. </del> <ins> This "recipe" for the Docker image will start from the official Node.js LTS image found on the Docker registry, expose port 8080, copy our `server.js` file to the image and start the Node server. </ins> Now build an image of your container by running `docker build`, tagging the image with the Google  Container Registry repo for your `PROJECT_ID`:

Discussion:
NodeJS 0.10 is going into security-only release mode very soon. The first version of 0.10 was released in March 2013, so it's over 3 years old. It would be great if we could update the tutorial/dockerfile to list the latest (or at least a newer) nodejs version.
Resolved by, thanks to
Change:
<ins> --- title: Istio id: istio date: 2018-04-12 full_link: https://istio.io/docs/concepts/what-is-istio/ short_description: > एक ओपन प्लैटफ़ॉर्म (कुबेरनेट्स-विशिष्ट नहीं) जो माइक्रोसर्विसेज को एकीकृत करने, ट्रैफ़िक प्रवाह को प्रबंधित करने, नीतियों को लागू करने और टेलीमेट्री डेटा को एकत्र करने का एक समान तरीका प्रदान करता हैं। aka: tags: - networking - architecture - extension --- एक ओपन प्लैटफ़ॉर्म (कुबेरनेट्स-विशिष्ट नहीं) जो माइक्रोसर्विसेज को एकीकृत करने, ट्रैफ़िक प्रवाह को प्रबंधित करने, नीतियों को लागू करने और टेलीमेट्री डेटा को एकत्र करने का एक समान तरीका प्रदान करता हैं। <!--more--> Istio को जोड़ने के लिए एप्लिकेशन कोड बदलने की आवश्यकता नहीं है। यह एक सर्विस और नेटवर्क के बीच बुनियादी ढांचे की एक परत है, जिसे जब सर्विस डिप्लॉयमेंट के साथ जोड़ा जाता है, तो इसे आमतौर पर सर्विस मैश (Service Mesh) के रूप में भी जाना जाता है। Istio का कंट्रोल प्लेन अंतर्निहित क्लस्टर प्रबंधन प्लैटफ़ॉर्म को अलग कर देता है, जो कुबेरनेट्स, Mesosphere आदि हो सकते हैं। </ins>

Discussion:
If this is your first contribution, visit for information on how to get started. Review a few to see which content you have to change and which you leave unchanged. Make sure your base, target branch is and create a working branch called . Create a file called Copy the content of to the file you created Localize the content. Push your change and create a pull request. Completing this feature issue fixes part of /language hi /triage accepted
/assign
Change:
- `kubectl edit cm kubelet-config-x.yy -n kube-system`を呼び出します(`x.yy`はKubernetesのバージョンに置き換えてください)。 - 既存の`cgroupDriver`の値を修正するか、以下のような新しいフィールドを追加します。 <del> ``yaml </del> <ins> ```yaml </ins> cgroupDriver: systemd ```

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: The code block is not being processed correctly, resulting in the page rendering in an unexpected way. <img width="625" alt="Screenshot 2023-12-06 at 16 52 11" src=""Proposed Solution: fix L84 (to yaml) 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
/language ja /assign
/area localization
Change:
* [Scheduler Policies](/docs/reference/scheduling/policies) * [Scheduler Profiles](/docs/reference/scheduling/config#profiles) <ins> * List of [ports and protocols](/docs/reference/ports-and-protocols/) that should be open on control plane and worker nodes </ins> ## Config APIs This section hosts the documentation for "unpublished" APIs which are used to

Discussion:
What would you like to be Create a dedicated ports and protocols page for Kubernetes Clusters. Why is this needed Currently, the closest page that provides this information is under KubeAdm install setup . This is hard to find for any cluster administrator trying to deploy Kubernetes Documented Ports for and are incorrect and need an update Slack thread: /sig security node docs architecture /area security
The label(s) cannot be applied, because the repository doesn't have them. <detailsIn response to : What would you like to be Create a dedicated ports and protocols page for Kubernetes Clusters. Currently, the closest page that provides this information is under KubeAdm install setup . This is hard to find for any cluster administrator trying to deploy Kubernetes Documented Ports for and are incorrect and need an update /area security 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
/triage accepted
Hi Would you be OK to have this as a reference page, rather than as a concept?
/sig network
/sig cluster-lifecycle Given the PR touches kubeadm docs.
Moved it under . This was the kind of feedback I was looking for from SIG Docs. Thank you
Change:
You should now be able to curl the nginx Service on `<CLUSTER-IP>:<PORT>` from any node in your cluster. Note that the Service IP is completely virtual, it never hits the wire. If you're curious about how this works you can read more <del> about the [service proxy](/docs/concepts/services-networking/service/#virtual-ips-and-service-proxies). </del> <ins> about the [service proxy](/docs/reference/networking/virtual-ips/). </ins> ## Accessing the Service

Discussion:
This is a Bug Report <!--Required Information--Problem: The under the in redirects to the following link: i.e. concept page in which there is nothing about Service Proxy. It is due to the revision of the Service concept page by the following PR: Proposed Solution: service proxy should redirect to instead of Page to Update:
/sig network /sig docs
I am working on the issue and will raise a PR soon. Thanks /assign
/triage accepted /priority backlog
Fixed it here:
Change:
With one of those specification, both an integer and a string validate. <del> In [Validation Schema Publishing](#publish-validation-schema-in-openapi-v2), </del> <ins> In [Validation Schema Publishing](#publish-validation-schema-in-openapi), </ins> `x-kubernetes-int-or-string: true` is unfolded to one of the two patterns shown above. ### RawExtension

Discussion:
This is a Bug Report Problem: The hyperlinks for OpenAPI validation schemas are also published and Validation Schema Publishing under the task page is not working. They both redirect to which is incorrect, the correct one is Proposed Solution: OpenAPI validation schemas are also published and Validation Schema Publishing should redirect to instead of Page to Update:
This issue is currently awaiting triage. SIG Docs takes a lead on issue triage for this website, but any Kubernetes member can accept issues by applying the label. The label can be by org members by writing in a comment. <detailsInstructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details
/assign
/sig api-machinery /language en /sig docs
Fixed the issue here:
Change:
A cluster consists of a master API server and a set of worker VMs called nodes. <del> Create a cluster via the Console: *Compute > Container Engine > Container Clusters > New container cluster*. Leave all the options default, and you should get a Kubernetes cluster with three nodes, ready to receive your container image. </del> <ins> Create a cluster via the Console: *Compute > Container Engine > Container Clusters > New container cluster*. Set the name to 'hello-world', leaving all other options default.  You should get a Kubernetes cluster with three nodes, ready to receive your container image. </ins> ![image](/images/hellonode/image_11.png)

Discussion:
When creating your cluster: "Leave all the options default, and you should get a Kubernetes cluster with three nodes, ready to receive your container image." ..should read: "Set the name to 'hello-world', leaving all other options default. You should get a Kubernetes cluster with three nodes, ready to receive your container image."
PR submitted:
cc
should be closed now
Change:
- Fetch all Pods in all namespaces using `kubectl get pods --all-namespaces` - Format the output to include only the list of Container image names <del> using `-o jsonpath={..image}`.  This will recursively parse out the </del> <ins> using `-o jsonpath={.items[*].spec.containers[*].image}`.  This will recursively parse out the </ins> `image` field from the returned json. - See the [jsonpath reference](/docs/reference/kubectl/jsonpath/) for further information on how to use jsonpath.

Discussion:
Hi, I've tested this example : It returns image names double, because "{..image}" recursively search in the output of JSON, So at the first, it will find the "image" word in "" and at the second time, it will find the "image" word in "". It means you will see the image name two times for each pod at least. Please change your example. Best Regards, Alireza Bahmani.
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
Hi What's the URL of the page where you've seen a problem?
here are the links to the: kubernetes docs website page ~ markdown file(s) where it require changes ~
The issue is, the following command produces 2 times (the count of image in a single pod). As mentioned, it is because the command count both the occurrence from the & sections from a single pod json manifest. Ideally it should be:
Following could be one of the fix for it:
/assign
There are other references . These would return duplicate images as well, right? I've updated those as well for now.
Hi yes, I feel those also need to be fixed. Let's wait for to provide their review. :)
Change:
### Authorization <del> [Authorization](/docs/reference/access-authn-authz/webhook/) determines whether specific users can read, write, and do other operations on API resources. It works at the level of whole resources -- it doesn't discriminate based on arbitrary object fields. If the built-in authorization options don't meet your needs, and [Authorization webhook](/docs/reference/access-authn-authz/webhook/) allows calling out to user-provided code to make an authorization decision. </del> <ins> [Authorization](/docs/reference/access-authn-authz/authorization/) determines whether specific users can read, write, and do other operations on API resources. It works at the level of whole resources -- it doesn't discriminate based on arbitrary object fields. If the built-in authorization options don't meet your needs, [Authorization webhook](/docs/reference/access-authn-authz/webhook/) allows calling out to user-provided code to make an authorization decision. </ins> ### Dynamic Admission Control

Discussion:
This is a Bug Report Problem: The link for Authorization under in is wrong. It is redirected to the which is wrong, It should redirect to Proposed Solution: We will have to use this link: for Authorization instead of . Page to Update:
/assign
Fixed it here:
Hey Do check on issue triage for this! Thank you.
/triage accepted
/language en
Change:
#### Metadatos de los Objectos <del> * [Annotations](/docs/concepts/overview/working-with-objects/annotations/) </del> <ins> * [Annotations](/es/docs/concepts/overview/working-with-objects/annotations/) </ins> ## {{% heading "whatsnext" %}} <del> Si estás interesado en escribir una página sobre conceptos, revisa [Usando Templates de Páginas](/docs/home/contribute/page-templates/) para obtener información sobre el tipo de página conceptos y la plantilla conceptos. </del> <ins> Si quieres empezar a contribuir a la documentación de Kubernetes accede a la página [Empieza a contribuir](/es/docs/contribute/start/). </ins>

Discussion:
This is a Bug Report concepts page for spanish links doesn't take to spanish pages <!--Required Information--Problem: The page is the Spanish translation, the links on this page should take you to the Spanish version of the link when available, if not available then ok to leave it pointing to English Proposed Solution: Update the page links to point to Spanish version (ie. es) Page to Update: I intended to review and 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
/language es
/assign
/assign
Thanks for the report, this is quite common as the translation is a work in progress and we don't have (yet) a way to easily detect where a page is referenced. Let me know if you have any issue working with the PR.
I will work on this page as one-off, and think about how can we automate the detection for all links that should point to the Spanish version.
Maybe something that can be done at build time? Don't know how is the site is build I guess Hugo but not how much pre-processing is done