jiebi/CodeConvo huggingface dataset:
Change:
#### Install wins, kubelet, and kubeadm ```PowerShell <del> curl.exe -LO https://github.com/kubernetes-sigs/sig-windows-tools/releases/latest/download/PrepareNode.ps1 </del> <ins> curl.exe -LO https://raw.githubusercontent.com/kubernetes-sigs/sig-windows-tools/master/kubeadm/scripts/PrepareNode.ps1 </ins> .PrepareNode.ps1 -KubernetesVersion {{< param "fullversion" >}} -ContainerRuntime containerD ```

Discussion:
Please change the link at ("Adding Windows nodes" page): with the new one:
Welcome and thanks for the first issue here! I will look into this issue. /assign
/triage accepted /kind bug
Instead you can request a new release in the sig windows tools repo, by logging an issue there. Linking to the master branch there is not a good idea, IMO. /sig windows
Also what problems are you seeing?
The problem is that the link is dead. We need to replace it with the link in
GitHub didn't allow me to assign the following users: steven-my. Note that only , repo collaborators and people who have commented on this issue/PR can be assigned. Additionally, issues/PRs can only have 10 assignees at the same time. For more information please see <detailsIn response to : /assign steven-my 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:
2. Download the Google Cloud public signing key: ```shell <del> sudo curl -fsSLo /etc/apt/keyrings/kubernetes-archive-keyring.gpg https://packages.cloud.google.com/apt/doc/apt-key.gpg </del> <ins> curl -fsSL https://packages.cloud.google.com/apt/doc/apt-key.gpg | sudo gpg --dearmor -o /etc/apt/keyrings/kubernetes-archive-keyring.gpg </ins> ``` 3. Add the Kubernetes `apt` repository:

Discussion:
It is easy to reproduce:
This seems to work: The was . A different solution would be to use , but is deprecated.
This issue is referring the same problem as in I think this will be helpful.
/language en /sig docs
Page related to issue: /kind bug
/retitle Unable to Install kubectl due to GPG Key Issue
We have made recent revisions to the documentation regarding the Google signing key for the installation page, as reflected in the pull request found at In order to resolve this issue, it will be necessary to make corresponding updates to the Kubectl installation instructions.
/triage accepted /priority important-soon
Please change: shell sudo curl -fsSLo /etc/apt/keyrings/kubernetes-archive- curl -fsSL | sudo gpg --dearmor -o /usr/share/keyrings/kubernetes-archive- /help
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 : Please change: sudo curl -fsSLo /etc/apt/keyrings/kubernetes-archive- curl -fsSL | sudo gpg --dearmor -o /usr/share/keyrings/kubernetes-archive- 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
would you be willing to edit the initial description for this issue, to make it easy to find: Code changes: link to )
I created a PR to update the docs.
I'd prefer a PR where the commit messages don't mention this issue. It's OK to mention the issue in the GitHub description of the change, but please don't mention the issue in commit messages.

If anyone would like to open a PR, similar to , that doesn't mention this issue in the commit message, then we can accept and merge that PR. Also you are welcome you amend to make it acceptable.
I have raised PR to assist in resolving this issue.
If you followed the guideline and you still get a error. You can do: then retry updating.
Change:
Patch your Deployment again with this new patch: ```shell <del> kubectl patch deployment retainkeys-demo --type merge --patch-file patch-file-retainkeys.yaml </del> <ins> kubectl patch deployment retainkeys-demo --type strategic --patch-file patch-file-retainkeys.yaml </ins> ``` Examine the content of the Deployment:

Discussion:
example commands are missing Resulting in: I will prepare a patch for this.
/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 : /triage accepted /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
Change:
extended tokens by starting `kube-apiserver` with flag `--service-account-extend-token-expiration=false`. Check [Bound Service Account Tokens](https://github.com/kubernetes/enhancements/blob/master/keps/sig-auth/1205-bound-service-account-tokens/README.md) for more details. <ins> - `ControllerManagerLeaderMigration`: Enables Leader Migration for [kube-controller-manager](/docs/tasks/administer-cluster/controller-manager-leader-migration/#initial-leader-migration-configuration) and [cloud-controller-manager](/docs/tasks/administer-cluster/controller-manager-leader-migration/#deploy-cloud-controller-manager) which allows a cluster operator to live migrate controllers from the kube-controller-manager into an external controller-manager (e.g. the cloud-controller-manager) in an HA cluster without downtime. </ins> - `CPUManager`: Enable container level CPU affinity support, see [CPU Management Policies](/docs/tasks/administer-cluster/cpu-management-policies/). - `CRIContainerLogRotation`: Enable container log rotation for CRI container runtime. The default max size of a log file is 10MB and the

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: doesn't list ControllerManagerLeaderMigration although there is a page that mentions it. Proposed Solution: Update / write the documentation for the feature, including a mention of in Page to Update: Additional Information: /sig cloud-provider
I think there's a plan to graduate this to beta; if so, we should definitely look at getting it properly documented.
yup, agreed. I think we can address it once they open a doc for their enhancement /cc /triage accepted
/assign
Change:
建议使用基于策略的准入插件（例如 [PodSecurityPolicy](#podsecuritypolicy) 和自定义准入插件）， 该插件可以针对特定用户或命名空间，还可以防止创建权限过高的 Pod。 <del> ### EventRateLimit {#eventratelimit} {{< feature-state for_k8s_version="v1.13" state="alpha" >}} </del> <ins> ### EventRateLimit {#eventratelimit} {{< feature-state for_k8s_version="v1.13" state="alpha" >}} </ins> <!-- This admission controller mitigates the problem where the API server gets flooded by

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: Page /zh/docs/reference/access-authn-authz/admission-controllers/ display abnormally, these anchor points should start on a new line. Proposed Solution: fix the anchor point format. abnormal format: normal format: Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--
/assign /language zh
Change:
* 安装 [kubectl](/zh/docs/tasks/tools/install-kubectl/). <del> * 使用 Google Kubernetes Engine 或 Amazon Web Services 等云供应商创建 Kubernetes 群集。 本教程创建了一个[外部负载均衡器](/zh/docs/tasks/access-application-cluster/create-external-load-balancer/)，需要云供应商。 </del> <ins> * 使用 Google Kubernetes Engine 或 Amazon Web Services 等云供应商创建 Kubernetes 集群。 本教程创建了一个[外部负载均衡器](/zh/docs/tasks/access-application-cluster/create-external-load-balancer/)， 需要云供应商。 </ins> * 配置 `kubectl` 与 Kubernetes API 服务器通信。有关说明，请参阅云供应商文档。 ## {{% heading "objectives" %}} <!-- * Run five instances of a Hello World application. * Create a Service object that exposes an external IP address. * Use the Service object to access the running application. --> * 运行 Hello World 应用程序的五个实例。 * 创建一个公开外部 IP 地址的 Service 对象。 * 使用 Service 对象访问正在运行的应用程序。 <!-- lessoncontent --> <!--

Discussion:
This is a Bug Report Chinese page contentzhdocstutorialsstateless-applicationexpose-external-ip- outdated <!-- 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: Chinese page contentzhdocstutorialsstateless-applicationexpose-external-ip- is different with English version page. Proposed Solution: Update Chinese page Page to Update: contentzhdocstutorialsstateless-applicationexpose-external-ip- <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--
/language zh
Issues go stale after 90d of inactivity. Mark the issue as fresh with . Stale issues rot after an additional 30d of inactivity and eventually close. If this issue is safe to close now please do so with . Send feedback to sig-testing, kubernetes/test-infra and/or . /lifecycle stale
Stale issues rot after 30d of inactivity. Mark the issue as fresh with . Rotten issues close after an additional 30d of inactivity. If this issue is safe to close now please do so with . Send feedback to sig-testing, kubernetes/test-infra and/or . /lifecycle rotten
/remove-lifecycle rotten
/assign
Change:
title: Kubernetesを拡張する weight: 110 description: Kubernetesクラスターの挙動を変えるいろいろな方法 <ins> feature: title: 拡張性を考慮した設計 description: > アップストリームのソースコードを変更することなく、Kubernetesクラスターに機能を追加できます。 </ins> content_type: concept no_list: true ---

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 enhanced? At feature section, Original K8s site contain 10 highlighted features and in "Ja" Localized version contain 9 highlighted features. That's the mismatch i wanted to address with this issue. ! !
/language ja /sig docs /area web-development
/assign
/assign
It looks no change on this issue for several months, so I remove the assignee. feel free to re-assign :) /unassign /unassign
/triage accepted
/assign
Target file: Japanese Localization document:
Thank you for your working!!
Change:
### PriorityLevelConfiguration <del> A PriorityLevelConfiguration represents a single isolation class. Each </del> <ins> A PriorityLevelConfiguration represents a single priority level. Each </ins> PriorityLevelConfiguration has an independent limit on the number of outstanding requests, and limitations on the number of queued requests.

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: Someone reading was not able to discern the intended meaning of the term "isolation class". See . This term is only used twice, and is used in a way that is synonymous with another term already introduced ("priority level"). I think it would be clearer to replace "isolation class" with "priority level". Proposed Solution: Replace "isolation class" with "priority level". Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--This has been there for a while. <!--Additional Information:--
/assign
/triage accepted
This is what I originally posted in the #api-priority-and-fairness Slack channel. Thanks for filing this on GitHub, Mike. !
Change:
Machine | 머신 | manifest | 매니페스트 | Master | 마스터 | <del> max limit/request ratio | 최대 상한/요청량 비율 | </del> metadata | 메타데이터 | metric | 메트릭 | masquerading | 마스커레이딩 |

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 .
Change:
extendedKeyUsage=serverAuth,clientAuth subjectAltName=@alt_names <del> <!-- 1.  Generate the certificate signing request based on the config file: --> 1.  基于上面的配置文件生成证书签名请求： </del> <ins> <!-- 5.  Generate the certificate signing request based on the config file: --> 5.  基于上面的配置文件生成证书签名请求： </ins> openssl req -new -key server.key -out server.csr -config csr.conf <del> <!-- 1.  Generate the server certificate using the ca.key, ca.crt and server.csr: --> 1.  基于 ca.key、ca.crt 和 server.csr 等三个文件生成服务端证书： </del> <ins> <!-- 6.  Generate the server certificate using the ca.key, ca.crt and server.csr: --> 6.  基于 ca.key、ca.crt 和 server.csr 等三个文件生成服务端证书： </ins> openssl x509 -req -in server.csr -CA ca.crt -CAkey ca.key  -CAcreateserial -out server.crt -days 10000  -extensions v3_ext -extfile csr.conf <del> <!-- 1.  View the certificate signing request: --> 1.  查看证书签名请求： </del> <ins> <!-- 7.  View the certificate signing request: --> 7.  查看证书签名请求： </ins> openssl req  -noout -text -in ./server.csr <del> <!-- 1.  View the certificate: --> 1.  查看证书： </del> <ins> <!-- 8.  View the certificate: --> 8.  查看证书： </ins> openssl x509  -noout -text -in ./server.crt

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:
Để tải về phiên bản cụ thể, hãy thay thế phần `$(curl -LS https://dl.k8s.io/release/stable.txt)` trong câu lệnh với phiên bản cụ thể. <del> Ví dụ, để tải về phiên bản {{< param "fullversion" >}} trên macOS, gõ: </del> <ins> Ví dụ, để tải về phiên bản {{< skew currentPatchVersion >}} trên macOS, gõ: </ins> ``` <del> curl -LO https://dl.k8s.io/release/{{< param "fullversion" >}}/bin/darwin/amd64/kubectl </del> <ins> curl -LO https://dl.k8s.io/release/v{{< skew currentPatchVersion >}}/bin/darwin/amd64/kubectl </ins> ``` 2. Tạo kubectl binary thực thi.

Discussion:
Problem: Based on , I have created this issue/task to help update the [vi] language documentation. Proposed Solution: Page to Update: In the branch, I found: Results for "fullversion" in "k8s-website/content/vi" /home/rdlugyhe/kubernetes/k8s-website/content/vi/docs/tasks/tools/install- 36: Ví dụ như, để tải về phiên bản {{< param "fullversion" }} trên Linux, hãy nhập như sau: 39: curl -LO {{< param "fullversion" }}/bin/linux/amd64/kubectl 111: Ví dụ, để tải về phiên bản {{< param "fullversion" }} trên macOS, gõ: 114: curl -LO {{< param "fullversion" }}/bin/darwin/amd64/kubectl 176: 1. Tải về phiên bản mới nhất {{< param "fullversion" }} từ đường dẫn nàyg
Change:
Download the kubectl-convert checksum file: ```powershell <del> curl -LO https://dl.k8s.io/{{< param "fullversion" >}}/bin/windows/amd64/kubectl-convert.exe.sha256 </del> <ins> curl -LO "https://dl.k8s.io/{{< param "fullversion" >}}/bin/windows/amd64/kubectl-convert.exe.sha256" </ins> ``` Validate the kubectl-convert 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:
``` Minikube contains a built-in Docker daemon that for running containers. <del> If you use another Docker daemon for building your containers, you will have to publish them to a registry before minikube can pull them. </del> <ins> If you use another Docker daemon for building your containers, you will have to publish them to a registry before minikube can pull them. </ins> You can use minikube's built in Docker daemon to avoid this extra step of pushing your images. Use the built-in Docker daemon with: ```shell eval $(minikube docker-env) ``` <del> This command sets up the Docker environment variables so a Docker client can communicate with the minikube Docker daemon: </del> <ins> This command sets up the Docker environment variables so a Docker client can communicate with the minikube Docker daemon. Minikube currently supports only docker version 1.11.1 on the server, which is what is supported by Kubernetes 1.3. With a newer docker version you'll get this [issue](https://github.com/kubernetes/minikube/issues/338). </ins> ```shell docker ps

Discussion:
Secrets and ConfigMap are logically siblings to one another and this should be reflected in the doc. Currently, the ConfigMap docs are linked to from 'Configuring Kubernetes' and the Secrets docs are linked only from the 'Concept Guide'. I suggest we do one of the following: Link from 'Concept Guide' to ConfigMap and remove the link to the ConfigMap docs from the 'Configuring Kubernetes' list Link from 'Configuring Kubernetes' to the Secrets docs and remove the link in the Concept Guide. We also need to add a stanza in the Concept Guide for ConfigMap, whether we link to the existing docs from there or not. Thoughs, ?
Added information on Secretes to ConfigMap, and they're both under the same header in guides. Should fix this the rest of the way with the site reorg.
Change:
* `SingleStack`: Single-stack service. The control plane allocates a cluster IP for the Service, using the first configured service cluster IP range. <del> * `PreferDualStack`: * Allocates IPv4 and IPv6 cluster IPs for the Service. * `RequireDualStack`: Allocates Service `.spec.ClusterIPs` from both IPv4 and IPv6 address ranges. </del> <ins> * `PreferDualStack`: Allocates both IPv4 and IPv6 cluster IPs for the Service when dual-stack is enabled. If dual-stack is not enabled or supported, it falls back to single-stack behavior. * `RequireDualStack`: Allocates Service `.spec.clusterIPs` from both IPv4 and IPv6 address ranges when dual-stack is enabled. If dual-stack is not enabled or supported, the Service API object creation fails. </ins> * Selects the `.spec.ClusterIP` from the list of `.spec.ClusterIPs` based on the address family of the first element in the `.spec.ipFamilies` array.

Discussion:
Hi k8s community, This issue refers to the documentation page, specifically to the "Services" chapter (link: ). The description of the field is missing relevant clarifications; here below what we have nowadays:: Allocates IPv4 and IPv6 cluster IPs for the Service. from both IPv4 and IPv6 address ranges. Selects the array. The current text for ) (note I used bold letters to remark the text) below), falling back to single-stack behavior if dual-stack not enabled/supported. from both IPv4 and IPv6 address ranges when dual-stack enabled, failing to create the Service API object if dual-stack not enabled/supported Selects the array.
Page reported in issue: /language en
/sig network
/triage accepted
Change:
/docs/home/contribute/generated-reference/kubernetes-components/ /docs/contribute/generate-ref-docs/kubernetes-components/ 301 /docs/home/contribute/localization/ /docs/contribute/localization/ 301 /docs/home/contribute/page-templates/ /docs/contribute/style/page-templates/ 301 <del> /docs/home/contribute/participating/ /docs/contribute/participating/ 301 </del> <ins> /docs/home/contribute/participating/ /docs/contribute/participate/ 301 </ins> /docs/home/contribute/review-issues/ /docs/contribute/intermediate/ 301 /docs/home/contribute/blog-post/ /docs/contribute/start/ 301 /docs/home/contribute/write-new-topic/ /docs/contribute/style/write-new-topic/ 301

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: "Not found" / 404 returned by Proposed Solution: Redirect to correct page at Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--Additional Info: Was actually testing and trying out some of the redirect rules and saw that these 2 return a 404: Opened a separate issue () for
/assign
Seems like the correct link is
/triage accepted
Change:
}] } <del> <!-- 1.  Generate CA key (`ca-key.pem`) and certificate (`ca.pem`): --> 1.  生成 CA 秘钥文件（`ca-key.pem`）和证书文件（`ca.pem`）： </del> <ins> <!-- 5.  Generate CA key (`ca-key.pem`) and certificate (`ca.pem`): --> 5.  生成 CA 秘钥文件（`ca-key.pem`）和证书文件（`ca.pem`）： </ins> ../cfssl gencert -initca ca-csr.json | ../cfssljson -bare ca <del> <!-- 1.  Create a JSON config file for generating keys and certificates for the API server, for example, `server-csr.json`. Be sure to replace the values in angle brackets with real values you want to use. The `MASTER_CLUSTER_IP` is the service cluster IP for the API server as described in previous subsection. The sample below also assumes that you are using `cluster.local` as the default DNS domain name. --> 1.  创建一个 JSON 配置文件，用来为 API 服务器生成秘钥和证书，例如：`server-csr.json`。 </del> <ins> <!-- 6.  Create a JSON config file for generating keys and certificates for the API server, for example, `server-csr.json`. Be sure to replace the values in angle brackets with real values you want to use. The `MASTER_CLUSTER_IP` is the service cluster IP for the API server as described in previous subsection. The sample below also assumes that you are using `cluster.local` as the default DNS domain name. --> 6.  创建一个 JSON 配置文件，用来为 API 服务器生成秘钥和证书，例如：`server-csr.json`。 </ins> 确认用你需要的值替换掉尖括号中的值。`MASTER_CLUSTER_IP` 是为 API 服务器 指定的服务集群 IP，就像前面小节描述的那样。 以下示例假定你的默认 DNS 域名为`cluster.local`。

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.