jiebi/CodeConvo huggingface dataset:
Change:
## Clean up <del> Run `kind delete cluster --name psa-with-cluster-pss` and `kind delete cluster --name psa-wo-cluster-pss` to delete the clusters you created. </del> <ins> Now delete the clusters which you created above by running the following command: ```shell kind delete cluster --name psa-with-cluster-pss ``` ```shell kind delete cluster --name psa-wo-cluster-pss ``` </ins> ## {{% heading "whatsnext" %}}

Discussion:
This is a Feature Request What would you like to be Add the commands which are under the Clean up section of the and tutorials into the shell code block snippet. Currently, it is under the triple backticks () as shown in the following screenshot: ! ! Which is not look more prominent. Why is this needed It provides a better structure to the section. and then it will be highlighted on the page. Comments None
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
/sig docs /language en
/assign
Fixed it here:
I'm not sure I agree with the issue description. I was nevertheless happy to merge the actual PR.
thank you, I opened this for the content so that commands under Cleanup should more clear like others command mentioned on the page.
Change:
```yaml apiVersion: rbac.authorization.k8s.io/v1 <del> # 此角色绑定使得用户 "dave" 能够读取 "default" 名字空间中的 Secrets </del> <ins> # 此角色绑定使得用户 "dave" 能够读取 "development" 名字空间中的 Secrets </ins> # 你需要一个名为 "secret-reader" 的 ClusterRole kind: RoleBinding metadata: name: read-secrets # RoleBinding 的名字空间决定了访问权限的授予范围。 <del> # 这里仅授权在 "development" 名字空间内的访问权限。 </del> <ins> # 这里隐含授权仅在 "development" 名字空间内的访问权限。 </ins> namespace: development subjects: - kind: User

Discussion:
! ! There is a problem with the Chinese version translated here, it should be in the "development" namespace.
/triage accepted /kind bug /assign
/language zh
Change:
--> <section id="users"> <del> <main> </del> <ins> <main class="main-section"> </ins> <!-- <h5>Kubernetes works with partners to create a strong, vibrant codebase that supports a spectrum of complementary platforms.</h5> --> <h5>Kubernetes 与合作伙伴携手打造一个强大、活跃的代码库，支持一系列互补平台。</h5> <div class="col-container"> <div class="col-nav"> <center> <del> <!-- <h5><b>Kubernetes Certified Service Providers</b></h5> --> <h5><b>Kubernetes 认证服务提供商</b></h5> </del> <ins> <h5> <!-- <b>Kubernetes Certified Service Providers</b> --> <b>Kubernetes 认证服务提供商</b> </h5> </ins> <!-- <br>Vetted service providers with deep experience helping enterprises successfully adopt Kubernetes. --> <br>经过审核的服务提供商在帮助企业成功采用 Kubernetes 方面有深厚的经验。 <br><br><br>

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: Missing partners in You can see to find the different. Proposed Solution: Update Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--
/language zh /assign
The label(s) cannot be applied, because the repository doesn't have them <detailsIn response to : /language zh /assign 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:
アクセスモードは次の通りです。 <del> * ReadWriteOnce –ボリュームは単一のNodeで読み取り/書き込みとしてマウントできます * ReadOnlyMany –ボリュームは多数のNodeで読み取り専用としてマウントできます * ReadWriteMany –ボリュームは多数のNodeで読み取り/書き込みとしてマウントできます </del> <ins> `ReadWriteOnce` : ボリュームは単一のNodeで読み取り/書き込みとしてマウントできます `ReadOnlyMany` : ボリュームは多数のNodeで読み取り専用としてマウントできます `ReadWriteMany` : ボリュームは多数のNodeで読み取り/書き込みとしてマウントできます `ReadWriteOncePod` : ボリュームは、単一のPodで読み取り/書き込みとしてマウントできます。クラスタ全体で1つのPodのみがそのPVCの読み取りまたは書き込みを行えるようにする場合は、ReadWriteOncePodアクセスモードを使用します。これは、CSIボリュームとKubernetesバージョン1.22以降でのみサポートされます。 これについてはブログ[Introducing Single Pod Access Mode for PersistentVolumes](/blog/2021/09/13/read-write-once-pod-access-mode-alpha/)に詳細が記載されています。 </ins> CLIではアクセスモードは次のように略されます。

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. --Apply the change which was by to Japanese website. Why is this needed The change which was by is not applied to Japanese page yet. 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:
# kubeadm-config.yaml kind: ClusterConfiguration apiVersion: kubeadm.k8s.io/v1beta2 <del> kubernetesVersion: v1.21 </del> <ins> kubernetesVersion: v1.21.0 </ins> --- kind: KubeletConfiguration apiVersion: kubelet.config.k8s.io/v1beta1

Discussion:
I'm at this page : If I follow the guide with the default configuration it will failed. The config from the webapge but if I remove the line : kubernetesVersion: v1.21 it will works. `
you should use the semver format is being followed by kubeadm and k8s. /kind support /close /sig cluster-lifecycle
Closing this issue. <detailsIn response to : kubernetesVersion: v1.21 /close /sig cluster-lifecycle </details
/reopen /remove-kind support actually...i see that you are reporting this as a problem on the page. we should change -there. /help
Reopened this issue. <detailsIn response to : /reopen /remove-kind support </details
you closed it too fast :) thanks to reopen it. I'll continue to filled issues each time a found a problem (second issue found in two days.. Happy to help the community)
sure, thanks for finding these. /triage accepted
PR is here /remove-help /lifecycle active
Change:
of cluster (node) autoscaling may cause voluntary disruptions to defragment and compact nodes. Your cluster administrator or hosting provider should have documented what level of voluntary disruptions, if any, to expect. Certain configuration options, such as <del> [using PriorityClasses](https://kubernetes.io/docs/concepts/configuration/pod-priority-preemption/) </del> <ins> [using PriorityClasses](/docs/concepts/configuration/pod-priority-preemption/) </ins> in your pod spec can also cause voluntary (and involuntary) disruptions.

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 href of contains unwanted . A slash () is missing in the href of . Proposed Solution: Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--/language en /assign
/triage accepted
Change:
{{< note >}} {{< feature-state state="deprecated" for_k8s_version="v1.11" >}} <del> This internal provisioner of OpenStack is deprecated. Please use [the external cloud provider for OpenStack](https://github.com/kubernetes/cloud-provider-openstack). </del> <ins> This internal provisioner of OpenStack is deprecated. Please use [the external cloud provider for OpenStack](https://github.com/kubernetes/cloud-provider-openstack). </ins> {{< /note >}} ### vSphere

Discussion:
There's a section for ReclaimPolicy, which states that this can be or . It is not clear as to what those states mean, there's NO explanation. I was researching how to expand disk, and one guide says that the must be , but I cannot find reference as to what this means. My expectation was that these would be explained what they mean, rather than this is the only do option.
Page related to issue: /retitle Lack of explanation for options - Retain and Delete /language en
These concepts are well explained in 'concepts/storage/persistent-'. Maybe a pointer or two suffices?
Please refer link here you will find the brief introduction about the retain or delete. I think this link will be helpful to understand.
/assign
/triage accepted
Change:
</tbody> </table> </div> <del> </div> </del>  No newline at end of file <ins> </div> {{- end -}} </ins>  No newline at end of file

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 Migrate to instead of Hugo's Why is this needed Upstream Hugo has deprecated , which we use. We should aim to migrate to use ; see Comments We may need to upgrade to a newer Hugo as part of this work, or related to it. /area web-development /lifecycle frozen
/triage accepted /priority backlog
Let me see if I can assist with this. Edit: Proposed fix in /assign
Change:
--- Allow setting the `restartPolicy` of an init container to `Always` so that the container becomes a sidecar container (restartable init containers). <del> See [Sidecar containers and restartPolicy](/docs/concepts/workloads/pods/init-containers/#sidecar-containers-and-restartpolicy) </del> <ins> See [Sidecar containers and restartPolicy](/docs/concepts/workloads/pods/sidecar-containers/) for more details. </ins>

Discussion:
This is a Bug Report Problem: text is no longer needed as sidecar containers are now entered into beta state and they are enable by default. reference link of sidecar containers present in page is wrongly redirecting to page. Proposed Solution: the text below from sidecar containers documentation. reference link present in page from page to page. Page to Update:
/sig docs /language en
/assign
Beta APIs are off by default with
is not a beta API though /triage accepted
Change:
{{< /comment >}} [NAT](https://en.wikipedia.org/wiki/Network_address_translation) <del> : network address translation </del> <ins> : Network address translation </ins> [Source NAT](https://en.wikipedia.org/wiki/Network_address_translation#SNAT) <del> : replacing the source IP on a packet; in this page, that usually means replacing with the IP address of a node. </del> <ins> : Replacing the source IP on a packet; in this page, that usually means replacing with the IP address of a node. </ins> [Destination NAT](https://en.wikipedia.org/wiki/Network_address_translation#DNAT) <del> : replacing the destination IP on a packet; in this page, that usually means replacing with the IP address of a {{< glossary_tooltip term_id="pod" >}} </del> <ins> : Replacing the destination IP on a packet; in this page, that usually means replacing with the IP address of a {{< glossary_tooltip term_id="pod" >}} </ins> [VIP](/docs/concepts/services-networking/service/#virtual-ips-and-service-proxies) <del> : a virtual IP address, such as the one assigned to every {{< glossary_tooltip text="Service" term_id="service" >}} in Kubernetes </del> <ins> : A virtual IP address, such as the one assigned to every {{< glossary_tooltip text="Service" term_id="service" >}} in Kubernetes </ins> [kube-proxy](/docs/concepts/services-networking/service/#virtual-ips-and-service-proxies) <del> : a network daemon that orchestrates Service VIP management on every node </del> <ins> : A network daemon that orchestrates Service VIP management on every node </ins> ### Prerequisites

Discussion:
Issue: Sentences under a subsection starts with small letters. Visit this link to see the issue: <img width="645" alt="Screenshot 2023-11-22 " src=""
/language en /sig docs
Yes i do agree that the sentence must be Capitalise and if the abbrevation of any word is address it should also be Capitalize in proper format. So that it look good to the reader.
/assign
/triage accepted
Change:
page for more on how to report vulnerabilities. <ins> ## What's next - [Security Checklist](/docs/concepts/security/security-checklist/) for additional information on Kubernetes security guidance. </ins>

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. --We have two pages with similar aims: We should ensure that the advice in the two documents is aligned, and also make sure that the two documents link to each other. Why is this needed It's a bad idea to document multiple ways to make sure that your cluster is secure, unless those are well aligned. Comments /sig security /sig docs /language en
Relevant to
Regarding this: We can use a reference section/note/what's next section in the end of stating: -
/triage accepted
Hey I would like to work on this.
/assign
Change:
应用可以在 Kubernetes 集群中安装一次或多次。在某些情况下，可以安装在同一命名空间中。例如，可以不止一次地为不同的站点安装不同的 WordPress。 <del> 应用的名称和实例的名称是分别记录的。例如，某 WordPress 实例的 `app.kubernetes.io/name` 为 `wordpress`，而其实例名称表现为 `app.kubernetes.io/instance` 的属性值 `wordpress-abcxzy`。这使应用程序和应用程序的实例成为可能是可识别的。应用程序的每个实例都必须具有唯一的名称。 </del> <ins> 应用的名称和实例的名称是分别记录的。例如，WordPress 应用的 `app.kubernetes.io/name` 为 `wordpress`，而其实例名称 `app.kubernetes.io/instance` 为 `wordpress-abcxzy`。 这使得应用和应用的实例均可被识别，应用的每个实例都必须具有唯一的名称。 </ins> <!-- ## Examples

Discussion:
WordPress wordpress wordpress-abcxzy
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 zh
/assign
Change:
### Jobs history limits <del> The `.spec.successfulJobsHistoryLimit` and `.spec.failedJobsHistoryLimit` fields are optional. These fields specify how many completed and failed Jobs should be kept. By default, they are set to 3 and 1 respectively.  Setting a limit to `0` corresponds to keeping none of the corresponding kind of Jobs after they finish. </del> <ins> The `.spec.successfulJobsHistoryLimit` and `.spec.failedJobsHistoryLimit` fields specify how many completed and failed Jobs should be kept. Both fields are optional. </ins> <del> For another way to clean up Jobs automatically, see [Clean up finished Jobs automatically](/docs/concepts/workloads/controllers/job/#clean-up-finished-jobs-automatically). </del> <ins> * `.spec.successfulJobsHistoryLimit`: This field specifies the number of successful finished jobs to keep. The default value is `3`. Setting this field to `0` will not keep any successful jobs. * `.spec.failedJobsHistoryLimit`: This field specifies the number of failed finished jobs to keep. The default value is `1`. Setting this field to `0` will not keep any failed jobs. For another way to clean up Jobs automatically, see [Clean up finished Jobs automatically](/docs/concepts/workloads/controllers/job/#clean-up-finished-jobs-automatically). </ins> ### Time zones

Discussion:
Does not describe the fields and , please add a list of all fields the spec can have, preferable with examples of use and format.
/triage accepted /kind feature
/retitle Mention and in CronJob concept page does link to which includes an explanation of these fields. /priority backlog /sig apps
/language en
Hmm, does not make sense to have these fields described by having to follow global doc link at the footer of the document. The exhaustive list of fields should be shown in the main page and for more information clearly linked to a detail page if needed. For starting users this is not clear and I can imagine for somebody not in the known you can only find this through the StackOverflow route. It also now fails to explain the possibilities of the definition as a person not aware of these fields is not informed of them as they would not know to look for them. Not a great Documentation Experience this way.
This issue is ready for a volunteer to work on it. Would anyone like to help out?
Let's add that This issue is now not about listing all the fields; for that, we already have (and that's why I changed the title of the issue)
There is a brief description of those fields in the document: are you asking for additional details? There isn't a lot more to say about them other than maybe rephrase it so it is more clear?
Rephrasing the page to be more clear would be a welcome improvement. Since this was filed, we've changed the page to link to the API reference from the right hand nav. We also have a long standing issue for , so work on this issue does not need to add a fact sheet. A brief tidy-up of the job history limit explanation would be fine to close this issue. if you're happy with the wording as-is, you are welcome to close the issue already.
/assign
Thanks see if you like the wording in the PR
Change:
and its [resource requirements](/docs/reference/kubernetes-api/workload-resources/pod-v1/#resources) * Read about [project quotas](https://xfs.org/index.php/XFS_FAQ#Q:_Quota:_Do_quotas_work_on_XFS.3F) in XFS * Read more about the [kube-scheduler configuration reference (v1beta3)](/docs/reference/config-api/kube-scheduler-config.v1beta3/) <del> * Read more about [Quality of Service classes for Pods](/docs/concepts/workloads/pods/pod-quality/) </del> <ins> * Read more about [Quality of Service classes for Pods](/docs/concepts/workloads/pods/pod-qos/) </ins>

Discussion:
This is a Bug Report Problem: The Hyperlink for under of and Containers gives Error. ! Proposed Solution: It should be redirected 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
/sig docs /language en
/assign
Fixed it here:
Change:
The [kubelet](/docs/reference/command-line-tools-reference/kubelet/) collects pod and container metrics via [cAdvisor](https://github.com/google/cadvisor). As an alpha feature, Kubernetes lets you configure the collection of pod and container <del> metrics via the {{< glossary_tooltip term_id="cri" text="Container Runtime Interface">}} (CRI). You </del> <ins> metrics via the {{< glossary_tooltip term_id="container-runtime-interface" text="Container Runtime Interface">}} (CRI). You </ins> must enable the `PodAndContainerStatsFromCRI` [feature gate](/docs/reference/command-line-tools-reference/feature-gates/) and use a compatible CRI implementation (containerd >= 1.6.0, CRI-O >= 1.23.0) to use the CRI based collection mechanism.

Discussion:
This is a Bug Report There is a wrong reference to the Container runtime interface in page. It take to container runtime instead of CRI. Should be updated with correct reference to CRI page.
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
/sig docs
/language en
/assign
fixed it
Change:
```powershell stop-service kube-proxy <del> curl.exe -Lo <kube-proxy.exe 路径> "https://dl.k8s.io/{{< skew currentPatchVersion >}}/bin/windows/amd64/kube-proxy.exe" </del> <ins> curl.exe -Lo <kube-proxy.exe 路径> "https://dl.k8s.io/v{{< skew currentPatchVersion >}}/bin/windows/amd64/kube-proxy.exe" </ins> restart-service kube-proxy ```

Discussion:
<!--Required Information--Problem: We've deprecated the param () and now English documents are using instead. (by ) All the other documents need to change into or appropriatly. Since several languages are involved, I'd like to share this issue to check all localizations complete the task. Proposed Solution: For each localization team, search and change appropriately. (See the reference, ) Please check the following task box if the localization task is complete. Page to Update: [x] de [x] es [x] fr [x] hi [x] id [x] ja [x] ko [x] pt-br [x] ru [x] vi [ ] zh-ch [previously done]Once all localizations have switched over, we can remove the parameter from the site.
/assign for the Korean contents.
PR: [ko] Replace deprecated fullversion shortcode for Korean :) The task for Korean can be completed after is merged into the main branch.
/assign For Brazilian Portuguese changes
/triage accepted
/assign For Hindi changes
The Brazilian Portuguese localization has replaced all occurrences via /.
/assign for french content
/reopen
Reopened this issue. <detailsIn response to : /reopen 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
/remove-help
I reopened as there is one more page to fix.
Really done! Thanks folks. /close
Closing this issue. <detailsIn response to : Really done! 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
Change:
DaemonSet | 데몬셋(DaemonSet) | API 오브젝트인 경우 Dashboard | 대시보드 | Data Plane | 데이터 플레인 | <del> Default Limit | 기본 상한 | Default Request | 기본 요청량 | </del> Deployment | 디플로이먼트(Deployment) | API 오브젝트인 경우 deprecated | 사용 중단(deprecated) | descriptor | 디스크립터, 식별자 |

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: / . '' '' . English | -- | -- Default Limit | Default Request | max limit/request ratio | / Resource Limit | Proposed Solution: / '' '' , . LimitRange API yaml English -- -- Default Limit Default Request max limit/request ratio Resource Limit limit ResourceQuota, LimitRange request ResourceQuota, LimitRange Page to Update: - <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--/language ko
/assign
. before : LimitRange after : ResourceQuota, LimitRange LimitRange ResourceQuota .