jiebi/CodeConvo huggingface dataset:
Change:
Here is the same information in a picture which shows how the pods might be placed on specific nodes. <del> ![Cluster](https://raw.githubusercontent.com/kubernetes/kubernetes/{{page.githubbranch}}/examples/blog-logging/diagrams/cloud-logging.png) </del> <ins> ![image](/images/blog-logging/diagrams/cloud-logging.png) </ins> This diagram shows four nodes created on a Google Compute Engine cluster with the name of each VM node on a purple background. The internal and public IPs of each node are shown on gray boxes and the pods running in each node are shown in green boxes. Each pod box shows the name of the pod and the namespace it runs in, the IP address of the pod and the images which are run as part of the pod's execution. Here we see that every node is running a fluentd-cloud-logging pod which is collecting the log output of the containers running on the same node and sending them to Google Cloud Logging. A pod which provides the [cluster DNS service](/docs/admin/dns) runs on one of the nodes and a pod which provides monitoring support runs on another node.

Discussion:
Here "Cluster" is a broken link: Perhaps this is an issue with : there is no in master branch, but there in branch. Same issue with below on the same page.
Change:
<br /> Then run <del> ```shell curl -L -o /etc/yum.repos.d/devel:kubic:libcontainers:stable.repo https://download.opensuse.org/repositories/devel:/kubic:/libcontainers:/stable/$OS/devel:kubic:libcontainers:stable.repo curl -L -o /etc/yum.repos.d/devel:kubic:libcontainers:stable:cri-o:$VERSION.repo https://download.opensuse.org/repositories/devel:kubic:libcontainers:stable:cri-o:$VERSION/$OS/devel:kubic:libcontainers:stable:cri-o:$VERSION.repo yum install cri-o ``` </del> --> <ins> 在下列操作系统上安装 CRI-O, 使用下表中合适的值设置环境变量 `OS`: </ins> <del> 要在以下操作系统上安装，请将环境变量 `$OS` 设置为下表中的相应字段： | 操作系统          | $OS               | | ---------------- | ----------------- | | Centos 8         | `CentOS_8`        | | Centos 8 Stream  | `CentOS_8_Stream` | | Centos 7         | `CentOS_7`        | </del> <ins> | 操作系统         | `$OS`             | |-----------------|-------------------| | Centos 8        | `CentOS_8`        | | Centos 8 Stream | `CentOS_8_Stream` | | Centos 7        | `CentOS_7`        | </ins> <br /> <del> 然后将 `$VERSION` 设置为与你的 Kubernetes 相匹配的 CRI-O 版本。 例如，如果要安装 CRI-O 1.18，请设置 `VERSION=1.18`。 你也可以安装特定版本，例如 1.18.3，请设置 `VERSION=1.18:1.18.3`。 </del> <ins> 然后，将 `$VERSION` 设置为与你的 Kubernetes 相匹配的 CRI-O 版本。 例如，如果你要安装 CRI-O 1.18, 请设置 `VERSION=1.18`. 你也可以安装一个特定的发行版本。 例如要安装 1.18.3 版本，设置 `VERSION=1.18:1.18.3`. </ins> <br /> <del> 确保声明变量后，使用下面命令安装 </del> <ins> 然后执行 </ins> ```shell <del> curl -L -o /etc/yum.repos.d/devel:kubic:libcontainers:stable.repo https://download.opensuse.org/repositories/devel:/kubic:/libcontainers:/stable/$OS/devel:kubic:libcontainers:stable.repo curl -L -o /etc/yum.repos.d/devel:kubic:libcontainers:stable:cri-o:$VERSION.repo https://download.opensuse.org/repositories/devel:kubic:libcontainers:stable:cri-o:$VERSION/$OS/devel:kubic:libcontainers:stable:cri-o:$VERSION.repo yum install cri-o </del> <ins> sudo curl -L -o /etc/yum.repos.d/devel:kubic:libcontainers:stable.repo https://download.opensuse.org/repositories/devel:/kubic:/libcontainers:/stable/$OS/devel:kubic:libcontainers:stable.repo sudo curl -L -o /etc/yum.repos.d/devel:kubic:libcontainers:stable:cri-o:$VERSION.repo https://download.opensuse.org/repositories/devel:kubic:libcontainers:stable:cri-o:$VERSION/$OS/devel:kubic:libcontainers:stable:cri-o:$VERSION.repo sudo yum install cri-o </ins> ``` {{% /tab %}}

Discussion:
With # merged, we are unable to track the changes to the in the English version. So this page needs a resync manually. /language zh
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
I'm gonna fixing this one if no other people working on this. /assign
Thank you very much,
Change:
{{< feature-state for_k8s_version="v1.8" state="beta" >}} <del> A _Cron Job_ creates [Jobs](/docs/concepts/workloads/controllers/jobs-run-to-completion/) on a time-based schedule. </del> <ins> A _CronJob_ creates {{< glossary_tooltip term_id="job" text="Jobs" >}} on a repeating schedule. </ins> One CronJob object is like one line of a _crontab_ (cron table) file. It runs a job periodically on a given schedule, written in [Cron](https://en.wikipedia.org/wiki/Cron) format.

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: This is the first one you get when searching docs for CronJob. I know this is a small suggestion but i think it would help a lot in reducing time searching / exploring kubectl explain. Proposed Solution: It should imho contain a example just like on the page: this would help to speed up search if needed fast. This example one: (copy paste from url) Page to Update:
This is similar to issue
Change:
# containerd 재시작 systemctl restart containerd ``` <del> {{< /tab >}} {{< tab name="CentOS/RHEL 7.4+" >}} </del> <ins> {{% /tab %}} {{% tab name="CentOS/RHEL 7.4+" %}} </ins> ```shell # (containerd 설치)

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: Broken layout for tabs on "Container runtimes" page as below. ! Proposed Solution: TBD Page to Update: /language ko <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--
/retitle Broken layout for tabs on "Container runtimes" page in Korean
This problem is due to incorrect tab code. We should fix this like the below: (Line 71, 125, 126, 180) to
/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
Hey folks, I'm happy to help you with this /assign
Change:
This page shows how to create a Pod that uses a Secret to pull an image from a private Docker registry or repository. ## {{% heading "prerequisites" %}} * {{< include "task-tutorial-prereqs.md" >}} {{< version-check >}} * To do this exercise, you need a [Docker ID](https://docs.docker.com/docker-id/) and password. <!-- steps --> ## Log in to Docker

Discussion:
This link "" appears to be broken in the line: " <your-registry-serveris your Private Docker Registry FQDN. ( for DockerHub) "
According to , the V1 API has been deprecated.
/triage accepted /assign
Change:
## {{% heading "whatsnext" %}} <del> * [attaching handlers to Container lifecycle events](/docs/tasks/configure-pod-container/attach-handler-lifecycle-event/)のハンズオンをやってみる </del> <ins> * [attaching handlers to Container lifecycle events](/ja/docs/tasks/configure-pod-container/attach-handler-lifecycle-event/)のハンズオンをやってみる </ins> * [Configure Liveness, Readiness and Startup Probes](/ja/docs/tasks/configure-pod-container/configure-liveness-readiness-startup-probes/)のハンズオンをやってみる <del> * [Container lifecycle hooks](/docs/concepts/containers/container-lifecycle-hooks/)についてもっと学ぶ </del> <ins> * [Container lifecycle hooks](/ja/docs/concepts/containers/container-lifecycle-hooks/)についてもっと学ぶ </ins> * APIのPod/コンテナステータスの詳細情報は[PodStatus](/docs/reference/generated/kubernetes-api/{{< param "version" >}}/#podstatus-v1-core)および[ContainerStatus](/docs/reference/generated/kubernetes-api/{{< param "version" >}}/#containerstatus-v1-core)を参照してください

Discussion:
This is a Feature Request <!-- Please only use this template for submitting feature/enhancement requests --<!-- See for guidance on writing an actionable issue description. --What would you like to be <!-- Describe as precisely as possible how this feature/enhancement should work from the user perspective. What should be changed, etc. --Update some links and fix some expressions. Why is this needed Some of the links have already been translated Also, some expressions were not official. Comments <!-- Any additional related comments that might help. Drawings/mockups would be extremely helpful (if required). --/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
Change:
<del> <?xml version="1.0"?> <svg width="476.1" height="385.3" xmlns="http://www.w3.org/2000/svg" xmlns:svg="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink"> <style type="text/css">.st0{fill:#FFFFFF;stroke:#006DE9;stroke-linecap:round;stroke-linejoin:round;stroke-miterlimit:10;} </del> <ins> <?xml version="1.0" encoding="UTF-8" standalone="no"?> <svg xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:cc="http://creativecommons.org/ns#" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:svg="http://www.w3.org/2000/svg" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" width="476.1" height="385.3" version="1.1" id="svg161"> <metadata id="metadata167"> <rdf:RDF> <cc:Work rdf:about=""> <dc:format>image/svg+xml</dc:format> <dc:type rdf:resource="http://purl.org/dc/dcmitype/StillImage" /> <dc:title></dc:title> </cc:Work> </rdf:RDF> </metadata> <defs id="defs165" /> <style type="text/css" id="style10">.st0{fill:#FFFFFF;stroke:#006DE9;stroke-linecap:round;stroke-linejoin:round;stroke-miterlimit:10;} </ins> .st1{fill:#FFFFFF;stroke:#006DE9;stroke-width:6;stroke-linecap:round;stroke-linejoin:round;stroke-miterlimit:10;} .st2{fill:#FFFFFF;stroke:#326DE6;stroke-width:2;stroke-linecap:round;stroke-linejoin:round;stroke-miterlimit:10;} .st3{opacity:0.71;fill:#326CE6;}

Discussion:
This is a Clean Up 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 Change to call the control plane a “control plane”, not a “master”. Why is this needed Kubernetes terms have changed: &hellip;however has not yet got that memo. This work would be part of The term “master” is unhelpful when it has connotations of being paired with “slave”. Comments Note that the diagrams also need revising at the same time (if need be, this could be 2 separate PRs that merge together). /language en /wg naming /kind cleanup
/assign
/triage accepted
Change:
have to be done by someone with root access to nodes. * All containers in a Pod are terminated while `restartPolicy` is set to Always, forcing a restart, and the init container completion record has been lost due <del> to garbage collection. </del> <ins> to {{< glossary_tooltip text="garbage collection" term_id="garbage-collection" >}}. </ins> The Pod will not be restarted when the init container image is changed, or the init container completion record has been lost due to garbage collection. This

Discussion:
This is a Bug Report Problem: section of page does not cover all required reference points which are mentioned throughout page. Proposed Solution: Add references of below topics under what's next section of page. learn about service, volume. kubelet, kubectl overview. Garbage Collection that Kubernetes uses to clean up cluster resources. Types of probes. Liveness, Readiness and Startup Probes. Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--
/sig docs /language en /assign
/remove-kind bug /triage accepted I'm not sure how much we need to tell people about Services and Volumes; maybe we should instead signpost readers to learn more about Pods in general - perhaps links to specific fragments of relevant Pod pages? Same for garbage collection really.
Thanks for reply. In that case i will add one link in general to know more about pods and service under What's next section. For garbage collection its already available under what's next section. So i will not add reference link inside page.
Oops! it was my mistake, there is no reference link provided for under what's next section. will add this too.
Hi , Below, i prepared the preview changes what i am planning to do as per my understanding based your comment above. I would like to confirm is these changes you were expecting to do for this issue. ! Please suggest.
Hi Could you please confirm on above comment.
Hi Could you please take a look on Hi Please confirm if these changes sounds good to you. So that i can go ahead and work on it, Thanks.
When adding links, please use links that have words like “volumes”; readers don't need to see the URL. If you send in a pull request we can offer feedback on it directly. Ideally we can accept it as is!
Thanks for your response, i will soon open a PR for it.
Fixed it here .
Change:
*  Implement audit rules that alert on specific events, such as concurrent reading of multiple Secrets by a single user <ins> #### Additional ServiceAccount annotations for Secret management You can also use the `kubernetes.io/enforce-mountable-secrets` annotation on a ServiceAccount to enforce specific rules on how Secrets are used in a Pod. For more details, see the [documentation on this annotation](/docs/reference/labels-annotations-taints/#enforce-mountable-secrets). </ins> ### Improve etcd management policies Consider wiping or shredding the durable storage used by `etcd` once it is

Discussion:
The documentation for the annotation on consists of : This leaves unclear the details of the actual effect of the annotation. By checking I was able to determine that setting this annotation to causes the following enforcements: (1) s mounted as must appear in the 's (2) s referenced in in or must appear in the 's (3) s referenced in of s must appear in the 's (1) is implied by the name of the annotation, but the lack of any mention of (2) or (3) in the documentation forced me to check the code to ensure that it wasn't only enforcing mounting of s as the name implies. The documentation also mentions only the field of the , yet the enforcement also takes into account the 's field (which the 's are checked against). The documentation would be improved by describing the actual enforcement behaviour that this feature implements. This feature may also benefit from being mentioned in the document.
/triage accepted /help /kind feature
This request has been marked as needing help from a contributor. Please ensure that the issue body includes answers to the following questions: Why are we solving this issue? To address this issue, are there any code changes? If there are code changes, what needs to be done in the code and what places can the assignee treat as reference points? Does this issue have zero to low barrier of entry? How can the assignee reach out to you for help? For more details on the requirements of such an issue, please see and ensure that they are met. If this request no longer meets these requirements, the label can be removed by commenting with the command. <detailsIn response to : /triage accepted /help /kind feature </details
I see , can come up with something like: I'll take this up?
/assign
Change:
## {{% heading "whatsnext" %}} <del> - [RuntimeClass Design](https://github.com/kubernetes/enhancements/blob/master/keps/sig-node/runtime-class.md) - [RuntimeClass Scheduling Design](https://github.com/kubernetes/enhancements/blob/master/keps/sig-node/runtime-class-scheduling.md) </del> <ins> - [RuntimeClass Design](https://github.com/kubernetes/enhancements/blob/master/keps/sig-node/585-runtime-class/README.md) - [RuntimeClass Scheduling Design](https://github.com/kubernetes/enhancements/blob/master/keps/sig-node/585-runtime-class/README.md#runtimeclass-scheduling) </ins> - Read about the [Pod Overhead](/docs/concepts/configuration/pod-overhead/) concept - [PodOverhead Feature Design](https://github.com/kubernetes/enhancements/blob/master/keps/sig-node/20190226-pod-overhead.md)

Discussion:
At the bottom of the page, in the section, the following links lead to a 404 page not found: RuntimeClass Design, link RuntimeClass Scheduling Design, link
Change:
#### My pod is crashing or otherwise unhealthy Once your pod has been scheduled, the methods described in [Debug Running Pods]( <del> /docs/tasks/debug/debug-applications/debug-running-pod/) are available for debugging. </del> <ins> /docs/tasks/debug/debug-application/debug-running-pod/) are available for debugging. </ins> #### My pod is running but not doing what I told it to do

Discussion:
Links to "Debugging Service" documents are not working. It is currently linking to when it should be
/triage accepted
Change:
in some namespaces.  However namespace resources are not themselves in a namespace. And low-level resources, such as [nodes](/docs/concepts/architecture/nodes/) and <del> persistentVolumes, are not in any namespace. </del> <ins> [persistentVolumes](/docs/concepts/storage/persistent-volumes/), are not in any namespace. </ins> To see which Kubernetes resources are and aren't in a namespace:

Discussion:
This is a Feature Request What would you like to be Under page, provide hyperlink for in section . Why is this needed it would be useful for quick reference. Comments /good-first-issue /language en /assign
I would like to work on this.
This issue isn't really well specified enough to be a good first issue. /triage accepted /remove-good-first-issue
Change:
apiVersion: v1 kind: ConfigMap metadata: <del> Name: game-demo </del> <ins> name: game-demo </ins> data: # 类属性键；每一个键都映射到一个简单的值 player_initial_lives: 3

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: apiVersion: v1 kind: ConfigMap metadata: Name: game-demo data: # playerinitiallives: 3 uipropertiesfile_name: "user-interface.properties" # # game.properties: | ,monsters player.maximum-lives=5 user-interface.properties: | allow.textmode=true Name: game-demo. name should be lower case Proposed Solution: Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--
/kind bug /priority backlog /language zh is incorrect in the manifest on it should be
/assign
Change:
| `IPv6DualStack` | `true` | Beta | 1.21 | | | `KubeletCredentialProviders` | `false` | Alpha | 1.20 | | | `LegacyNodeRoleBehavior` | `false` | Alpha | 1.16 | 1.18 | <del> | `LegacyNodeRoleBehavior` | `true` | True | 1.19 |  | </del> <ins> | `LegacyNodeRoleBehavior` | `true` | Beta | 1.19 |  | </ins> | `LocalStorageCapacityIsolation` | `false` | Alpha | 1.7 | 1.9 | | `LocalStorageCapacityIsolation` | `true` | Beta | 1.10 | | | `LocalStorageCapacityIsolationFSQuotaMonitoring` | `false` | Alpha | 1.15 | |

Discussion:
Problem: Incorrect stage values in FeatureGate documentation LegacyNodeRoleBehavior has a stage of as of 1.19, which is not a valid stage. WindowsEndpointSliceProxying has a stage of as of 1.21; all other stage values are capitalized. Feature Until -- -- LegacyNodeRoleBehavior 1.19 WindowsEndpointSliceProxying Proposed Solution: Correct Stage text for listed FeatureGates Page to Update:
~That's not what I see on that page. Can you include a screenshot and confirm the URL you're viewing ?~ ~If possible, it'd be useful to see the HTTP headers that go with the page you screenshotted.~ I see it!
/triage accepted /language en /priority backlog /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 : /triage accepted /language en /priority backlog /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
Thanks
Is the change for from to , to and add to ?
AIUI the change for is: change the column from to and the change for is: change the column from to no other changes needed
Change:
If CPU and memory limits are not specified for a container, and you use the downward API to try to expose that information, then the kubelet defaults to exposing the maximum allocatable value for CPU and memory <del> (based on the [node allocatable](/docs/tasks/administer-cluster/reserve-compute-resources/#node-allocatable) calculation). </del> <ins> based on the [node allocatable](/docs/tasks/administer-cluster/reserve-compute-resources/#node-allocatable) calculation. </ins> ## {{% heading "whatsnext" %}}

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 downward API page writes “error prone”, where “error-prone” would send a much more clear context signal to localization teams. Proposed Solution: Add the missing character. The page was recently updated so no other changes are needed; however, it would super useful to include the other fix from The other change is to remove the parens around: (from the same page!) Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--Additional Information: /kind cleanup /language en /good-first-issue /priority backlog /triage accepted
This request has been marked as suitable for new contributors. Please ensure that the issue body includes answers to the following questions: Why are we solving this issue? To address this issue, are there any code changes? If there are code changes, what needs to be done in the code and what places can the assignee treat as reference points? Does this issue have zero to low barrier of entry? How can the assignee reach out to you for help? For more details on the requirements of such an issue, please see and ensure that they are met. If this request no longer meets these requirements, the label can be removed by commenting with the command. <detailsIn response to : This is a Bug Report <!-- See for guidance on writing an actionable issue description. --Problem: The downward API page writes “error prone”, where “error-prone” would send a much more clear context signal to localization teams. Add the missing character. The page was recently updated so no other changes are needed; however, it would super useful to include the other fix from The other change is to remove the parens around: based on the calculation <!--Kubernetes Version:--/kind cleanup /language en /good-first-issue /priority backlog /triage accepted </details
/assign