jiebi/CodeConvo huggingface dataset:
Change:
See [Certificate Signing Requests](/docs/reference/access-authn-authz/certificate-signing-requests/) for more information on the permissions required to perform different actions on CertificateSigningRequest resources. <del> ### CertificateSubjectRestrictions {#certificatesubjectrestrictions} </del> <ins> ### CertificateSubjectRestriction {#certificatesubjectrestriction} </ins> This admission controller observes creation of CertificateSigningRequest resources that have a `spec.signerName` of `kubernetes.io/kube-apiserver-client`. It rejects any request that specifies a 'group' (or 'organization attribute')

Discussion:
Simple documentation issue: Section for "CertificateSubjectRestriction" admission controller is "CertificateSubjectRestrictions". The appended 's' is not valid and will prevent apiserver startup if used in --disable-admission-plugins. Note: plugin is listed correctly in the 'defaults' list.
Fixed by /close
Closing this issue. <detailsIn response to : Fixed by /close 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 /language en
Change:
また、[`kubectl`リファレンスドキュメント](/ja/docs/reference/kubectl/)も参照できます。 <del> ## Minikube </del> <ins> ## minikube </ins> <del> [Minikube](https://minikube.sigs.k8s.io/)は、Kubernetesをローカルで実行するツールです。MinikubeはシングルノードのKubernetesクラスターをパーソナルコンピューター上(Windows、macOS、Linux PCを含む)で実行することで、Kubernetesを試したり、日常的な開発作業のために利用できます。 </del> <ins> [minikube](https://minikube.sigs.k8s.io/)は、Kubernetesをローカルで実行するツールです。minikubeはシングルノードのKubernetesクラスターをパーソナルコンピューター上(Windows、macOS、Linux PCを含む)で実行することで、Kubernetesを試したり、日常的な開発作業のために利用できます。 </ins> ツールのインストールについて知りたい場合は、公式の[Get Started!](https://minikube.sigs.k8s.io/docs/start/)のガイドに従ってください。 <del> Minikubeが起動したら、[サンプルアプリケーションの実行](/ja/docs/tutorials/hello-minikube/)を試すことができます。 </del> <ins> minikubeが起動したら、[サンプルアプリケーションの実行](/ja/docs/tutorials/hello-minikube/)を試すことができます。 </ins> ## kind <del> Minikubeと同じように、[kind](https://kind.sigs.k8s.io/docs/)もローカルコンピューター上でKubernetesを実行するツールです。Minikubeとは違い、kindは1種類のコンテナランタイム上でしか動作しません。実行には[Docker](https://docs.docker.com/get-docker/)のインストールと設定が必要です。 </del> <ins> minikubeと同じように、[kind](https://kind.sigs.k8s.io/docs/)もローカルコンピューター上でKubernetesを実行するツールです。minikubeとは違い、kindは1種類のコンテナランタイム上でしか動作しません。実行には[Docker](https://docs.docker.com/get-docker/)のインストールと設定が必要です。 </ins> [Quick Start](https://kind.sigs.k8s.io/docs/user/quick-start/)に、kindの起動に必要な手順が説明されています。

Discussion:
This is a Feature Request In the documentation available in , as well as in the link, the term is written as . I'd like to suggest updating it to to align with the and . <!-- 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 occurrences of to . Why is this needed Using the incorrect casing can be misleading, especially for newcomers. Comments <!-- Any additional related comments that might help. Drawings/mockups would be extremely helpful (if required). --
/assign
/language ja
/triage accepted
Change:
certificates by requesting them from the `certificates.k8s.io` API. One known limitation is that the CSRs (Certificate Signing Requests) for these certificates cannot be automatically approved by the default signer in the kube-controller-manager - <del> [`kubernetes.io/kubelet-serving`](https://kubernetes.io/docs/reference/access-authn-authz/certificate-signing-requests/#kubernetes-signers). </del> <ins> [`kubernetes.io/kubelet-serving`](/docs/reference/access-authn-authz/certificate-signing-requests/#kubernetes-signers). </ins> This will require action from the user or a third party controller. These CSRs can be viewed using:

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:
<ins> #!/bin/bash #!/usr/bin/env bash # This script reproduces what the kubelet does # to calculate memory.available relative to root cgroup. # current memory usage memory_capacity_in_kb=$(cat /proc/meminfo | grep MemTotal | awk '{print $2}') memory_capacity_in_bytes=$((memory_capacity_in_kb * 1024)) memory_usage_in_bytes=$(cat /sys/fs/cgroup/memory/memory.usage_in_bytes) memory_total_inactive_file=$(cat /sys/fs/cgroup/memory/memory.stat | grep total_inactive_file | awk '{print $2}') memory_working_set=${memory_usage_in_bytes} if [ "$memory_working_set" -lt "$memory_total_inactive_file" ]; then memory_working_set=0 else memory_working_set=$((memory_usage_in_bytes - memory_total_inactive_file)) fi memory_available_in_bytes=$((memory_capacity_in_bytes - memory_working_set)) memory_available_in_kb=$((memory_available_in_bytes / 1024)) memory_available_in_mb=$((memory_available_in_kb / 1024)) echo "memory.capacity_in_bytes $memory_capacity_in_bytes" echo "memory.usage_in_bytes $memory_usage_in_bytes" echo "memory.total_inactive_file $memory_total_inactive_file" echo "memory.working_set $memory_working_set" echo "memory.available_in_bytes $memory_available_in_bytes" echo "memory.available_in_kb $memory_available_in_kb" echo "memory.available_in_mb $memory_available_in_mb" </ins>

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 broken link to script in tasks/administer-cluster/out-of- file. At 44 line: Proposed Solution: Move the script file to examples directory. Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--/language en
/assign
Change:
body { background-color: white; <ins> a { color: $blue; } </ins> } section {

Discussion:
This is a Bug Report Links within the tab component are not displaying using the site link color. Problem: The color of links within tab components is defaulting to . The link is inheriting the color value from jquery-ui- Proposed Solution: Update the style for ui-widget-content -a Page to Update: Start by looking at . Examples: See link in Flatcar Container Linux tab in Look as the "vSphere" tab at the bottom of the page.
Related to PR .
/kind bug /priority backlog /area web-development Feel free to reprioritize
/assign
Change:
Download the kubectl checksum file: ```powershell <del> curl -LO https://dl.k8s.io/{{< param "fullversion" >}}/bin/windows/amd64/kubectl.exe.sha256 </del> <ins> curl -LO "https://dl.k8s.io/{{< param "fullversion" >}}/bin/windows/amd64/kubectl.exe.sha256" </ins> ``` Validate the kubectl binary against the checksum file:

Discussion:
Very basic step "Install kubectl binary with curl on Windows" Response seems good: But .exe is actually XML, giving download error: Hard to realize and quite unfriendly! Thanks
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
/kind bug There are multiple broken links on this page. It seems the links on this page is missing the version from it
/assign
Change:
with `NoExecute` effect. If the fault condition returns to normal the kubelet or node controller can remove the relevant taint(s). <ins> In some cases when the node is unreachable, the API server is unable to communicate with the kubelet on the node. The decision to delete the pods cannot be communicated to the kubelet until communication with the API server is re-established. In the meantime, the pods that are scheduled for deletion may continue to run on the partitioned node. </ins> {{< note >}} The control plane limits the rate of adding node new taints to nodes. This rate limiting manages the number of evictions that are triggered when many nodes become unreachable at

Discussion:
This page talks about but the page referred does not contain anything about . Looks like either Nodes is outdated or kube-controller-manager is missing this documentation.
Page:
was deprecated in k8s v1.26 and will remove in k8s v1.27 Here is the PR:
As it is deprecated we have to mention this as a note in the docs for v1.26 and in v1.27, remove this from the docs. Let's wait for others members, what they think about it.
/kind bug /sig apps
/retitle Stale or incorrect information in Nodes concept page
/remove-sig apps It's nice if people who deprecate a thing also track a docs update issue. However, I wouldn't expect SIG Apps to pick this up.
yeah, that will be really helpful.
/triage accepted
Could you please take a look?
/triage accepted
/assign
thanks for the PR. It is Ok for v1.27. But I have one concern regarding v1.26 if we click on as mentioned above, we can't find as it is deprecated in v1.26. Either we have to remove this from v1.26 also or mention the Note in v1.26 docs regarding the depreciation.
It is mentioned under till k8s v1.25. Here is the following link for it: https://v1-
Hi , Your thoughts on this
This issue has not been updated in over 1 year, and should be re-triaged. You can: Confirm that this issue is still relevant with (org members only) Close this issue with For more details on the triage process, see /remove-triage accepted
closing this issue, as it was resolved by PR /close
Closing this issue. <detailsIn response to : closing this issue, as it was resolved by PR 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:
<!-- ## Use foreground cascading deletion {#use-foreground-cascading-deletion} <del> By default, Kubernetes uses [background cascading deletion](/docs/concepts/workloads/controllers/garbage-collection/#background-deletion) </del> <ins> By default, Kubernetes uses [background cascading deletion](/docs/concepts/architecture/garbage-collection/#background-deletion) </ins> to delete dependents of an object. You can switch to foreground cascading deletion using either `kubectl` or the Kubernetes API, depending on the Kubernetes version your cluster runs. {{<version-check>}} --> ## 使用前台级联删除    {#use-foreground-cascading-deletion} <del> 默认情况下，Kubernetes 使用[后台级联删除](/zh/docs/concepts/workloads/controllers/garbage-collection/#background-deletion) </del> <ins> 默认情况下，Kubernetes 使用[后台级联删除](/zh/docs/concepts/architecture/garbage-collection/#background-deletion) </ins> 以删除依赖某对象的其他对象。取决于你的集群所运行的 Kubernetes 版本， 你可以使用 `kubectl` 或者 Kubernetes API 来切换到前台级联删除。 {{<version-check>}}

Discussion:
There is a bug: ,%E4%BA%86%E8%A7%A3%E5%9E%83%E5%9C%BE%E6%94%B6%E9%9B%86.,-%E5%8F%8D%E9%A6%88 This hyperlink is 404, it should be ""
/assign
/triage accepted
The issue was solved by PR . If there is any problem, please give feedback again. /close
Closing this issue. <detailsIn response to : The issue was solved by PR . If there is any problem, please give feedback again. /close 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:
These guides are maintained by community members, cover specific platforms and use cases, and experiment with different ways of configuring Kubernetes on CoreOS. <del> [**Multi-node Cluster**](/docs/getting-started-guides/coreos/coreos_multinode_cluster) Set up a single master, multi-worker cluster on your choice of platform: AWS, GCE, or VMware Fusion. <hr/> </del> [**Easy Multi-node Cluster on Google Compute Engine**](https://github.com/rimusz/coreos-multi-node-k8s-gce/blob/master/README.md) Scripted installation of a single master, multi-worker cluster on GCE. Kubernetes components are managed by [fleet](https://github.com/coreos/fleet).

Discussion:
A user linked to this guide from an issue: I believe that guide is unmaintained. It still specifies k8s 1.1.2. can we delete?
Thank you. Yes, this guide was unmaintained and community contributed. I am OK with this change. devin-donnelly wrote:
Change:
Create the Pod: --> <del> 在这个配置文件中，你可以看到 Pod 有一个 `downwardAPI` 类型的卷，并且挂载到容器的 `/etc/podinfo` 目录。 </del> <ins> 在这个配置文件中，你可以看到 Pod 有一个 `downwardAPI` 类型的卷，并且挂载到容器的 `/etc/podinfo` 目录。 </ins> 查看 `downwardAPI` 下面的 `items` 数组。每个数组元素都是一个 DownwardAPIVolumeFile。

Discussion:
the file labels and annotations should be in the directory /etc/podinfo not /etc !
Hi What's the URL of the web page that isn't right? /triage needs-information
/triage accepted
/assign
Change:
runtime_path = "${PATH_TO_BINARY}" ``` <del> 詳細はCRI-Oの[設定に関するドキュメント](https://raw.githubusercontent.com/cri-o/cri-o/9f11d1d/docs/crio.conf.5.md)を参照してください。 </del> <ins> 詳細はCRI-Oの[設定に関するドキュメント](https://github.com/cri-o/cri-o/blob/master/docs/crio.conf.5.md)を参照してください。 </ins> ## スケジューリング {#scheduling} {{< feature-state for_k8s_version="v1.16" state="beta" >}} <del> Kubernetes 1.16では、RuntimeClassは`scheduling`フィールドを使ったクラスター内での異なる設定をサポートしています。 このフィールドによって、設定されたRuntimeClassをサポートするノードに対してPodがスケジュールされることを保証できます。 スケジューリングをサポートするためにはRuntimeClass [アドミッションコントローラー](/docs/reference/access-authn-authz/admission-controllers/#runtimeclass)を有効にしなければなりません。(1.16ではデフォルトです) </del> <ins> RuntimeClassの`scheduling`フィールドを指定することで、設定されたRuntimeClassをサポートするノードにPodがスケジューリングされるように制限することができます。 `scheduling`が設定されていない場合、このRuntimeClassはすべてのノードでサポートされていると仮定されます。 </ins> 特定のRuntimeClassをサポートしているノードへPodが配置されることを保証するために、各ノードは`runtimeclass.scheduling.nodeSelector`フィールドによって選択される共通のラベルを持つべきです。 RuntimeClassのnodeSelectorはアドミッション機能によりPodのnodeSelectorに統合され、効率よくノードを選択します。

Discussion:
This is a Feature Request What would you like to be We need to update content/ja/docs/concepts/containers/runtime- according to the English text, because it is outdated. Why is this needed content/ja/docs/concepts/containers/runtime- is outdated. Comments /language ja /assign
/triage accepted
Change:
### container.seccomp.security.alpha.kubernetes.io/[NAME] {#container-seccomp-security-alpha-kubernetes-io} This annotation has been deprecated since Kubernetes v1.19 and will become non-functional in v1.25. <del> The tutorial [Restrict a Container's Syscalls with seccomp](/docs/tutorials/clusters/seccomp/) takes </del> <ins> The tutorial [Restrict a Container's Syscalls with seccomp](/docs/tutorials/security/seccomp/) takes </ins> you through the steps you follow to apply a seccomp profile to a Pod or to one of its containers. That tutorial covers the supported mechanism for configuring seccomp in Kubernetes, based on setting `securityContext` within the Pod's `.spec`.

Discussion:
This is a Bug Report There is a link /docs/tutorials/clusters/seccomp on line 481 of the page content endocsreferencelabels-annotations-,but this link does not exist. <!--Required Information--Problem: There is a link /docs/tutorials/clusters/seccomp on line 481 of the page contentendocsreferencelabels-annotations-,but this link does not exist. Proposed Solution: commented redirects to We should update so that it hyperlinks to instead. Page to Update: <!--Kubernetes Version:--v1.23 <!--Additional Information:--NA Comments /language zh /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
Already done, next time we can use in PR description to auto close this. /close
Closing this issue. <detailsIn response to : Already done, next time we can use in PR description to auto close this. 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:
--> ### cloud-controller-manager <ins> {{< glossary_definition term_id="cloud-controller-manager" length="short" >}} </ins> `cloud-controller-manager` 进运行特定于云平台的控制回路。 如果你在自己的环境中运行 Kubernetes，或者在本地计算机中运行学习环境， 所部属的环境中不需要云控制器管理器。

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: Original text hast been kept along with translated text Proposed Solution: Delete original English text Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--<img width="863" alt="" src="https://user-"
Looks like the is still working even when being commented out. I have encountered this a hundred times when tidying up the Chinese localization, and this is one of the reasons I don't like this shortcode.
/assign
Change:
} } <del> <!-- 1.  Create a JSON config file for CA certificate signing request (CSR), for example, `ca-csr.json`. Be sure to replace the values marked with angle brackets with real values you want to use. --> 1.  创建一个 JSON 配置文件，用于 CA 证书签名请求（CSR），例如：`ca-csr.json`。 </del> <ins> <!-- 4.  Create a JSON config file for CA certificate signing request (CSR), for example, `ca-csr.json`. Be sure to replace the values marked with angle brackets with real values you want to use. --> 4.  创建一个 JSON 配置文件，用于 CA 证书签名请求（CSR），例如：`ca-csr.json`。 </ins> 确认用你需要的值替换掉尖括号中的值。 {

Discussion:
Link to The secondary list elements in the page are all "1." , they are not in order, it looks weird
/sig docs
Hi can you please elaborate which page are you talking about?
Sorry, I forgot to check the link in my issue, the correct link is
/language zh /triage accepted /retitle [zh] Wrong list numbering in page FYI: Page to update: page: file:
/assign
/assign
This fixes this issue.
please avoid assigning yourself to a issue that is already assigned to somebody else.
Change:
### Configure TLS Worker nodes require three keys: `ca.pem`, `worker.pem`, and `worker-key.pem`.  We've already generated <del> `ca.pem` for use on the Master.  The worker public/private keypair should be generated for each Kubernetes node. </del> <ins> `ca.pem` and `ca-key.pem` for use on the Master.  The worker public/private keypair should be generated for each Kubernetes node. </ins> 1.  Create the file `worker-openssl.cnf` with the following contents.

Discussion:
Step 2 of says that it uses the generated earlier. In fact it also uses the ca- generated earlier.
Change:
下表列出所有受支持的资源类型及其缩写别名: <!-- <del> (This output can be retrieved from `kubectl api-resources`, and is accurate as of Kubernetes 1.13.3.) </del> <ins> (This output can be retrieved from `kubectl api-resources`, and is accurate as of Kubernetes 1.19.1.) </ins> --> <del> (以下输出可以通过 `kubectl api-resources` 获取，内容以 Kubernetes 1.13.3 版本为准。) </del> <ins> (以下输出可以通过 `kubectl api-resources` 获取，内容以 Kubernetes 1.19.1 版本为准。) </ins> <!-- <del> | Resource Name | Short Names | API Group | Namespaced | Resource Kind | </del> <ins> | NAME | SHORTNAMES | APIGROUP | NAMESPACED | KIND | </ins> |---|---|---|---|---| <ins> | `bindings` | | | true | Binding | </ins> | `componentstatuses` | `cs` | | false | ComponentStatus | | `configmaps` | `cm` | | true | ConfigMap | | `endpoints` | `ep` | | true | Endpoints | <ins> | `events` | `ev` | | true | Event | </ins> | `limitranges` | `limits` | | true | LimitRange | | `namespaces` | `ns` | | false | Namespace | | `nodes` | `no` | | false | Node |

Discussion:
This is a Bug Report Problem: The resource type list on is about v1.13.3 which is too old. We are not obliged to keep the list updated on every release, but having the list updated to a supported version is still desireable. Proposed Solution: Update the list to reflect what we have today. Page to Update:
ref:
/assign
fixed. /close
Closing this issue. <detailsIn response to : fixed. /close 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:
"name-virtual-host-ingress-no-third-host": {&networking.Ingress{}}, "namespaced-params":                       {&networking.IngressClass{}}, "networkpolicy":                           {&networking.NetworkPolicy{}}, <ins> "networkpolicy-multiport-egress":          {&networking.NetworkPolicy{}}, </ins> "network-policy-allow-all-egress":         {&networking.NetworkPolicy{}}, "network-policy-allow-all-ingress":        {&networking.NetworkPolicy{}}, "network-policy-default-deny-egress":      {&networking.NetworkPolicy{}},

Discussion:
I spent one hour to do one sample exercice about network policy because of your wrong configuration !!! +++++++++++++++++++++ policyTypes: # should remove space in the 2nd & 3rd line Ingress Egress ++++++++++++++++++++++ egress: to: ipBlock: cidr: 10.0.0.0/24 ports: # "-" is missing before ports protocol: TCP port: 5978
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 Invalid manifest in Network Policies page Thanks for reporting the bug /kind bug /language en Please paste in the entire invalid manifest (surround it by <tt`</ttif you can) so we know which part of the page is wrong. We could guess, but it's easier if you're explicit about this
/triage accepted /assign
Change:
<!-- Use the output from the previous commands to create a yaml file as follows. The base64 encoded value should all be on a single line. --> <del> 使用前面命令的输出来创建yaml文件，如下所示。 base64编码的值应全部放在一行上。 </del> <ins> 使用前面命令的输出来创建 yaml 文件，如下所示。 base64 编码的值应全部放在一行上。 </ins> ```yaml apiVersion: "v1"

Discussion:
Nginx https 404
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 It sounds like you wanted to provide feedback about a web page. Which web page was that? /triage needs-information