jiebi/CodeConvo huggingface dataset:
Change:
Several of the types used in AdmissionRequest does not seem to be documented anywhere. The links point to the general Kubernetes API docs, but the actual types does not seem to be defined there. Searching in the docs does not turn up any obvious references, and neither does web searches. Types missing documentation:
/sig docs /language en
Yes, no documentation for and But for , it should be . The doc is here:
/triage accepted /assign

Discussion:
</td> </tr> <tr><td><code>kind</code> <B>[Required]</B><br/> <del> <a href="https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.27/#groupversionkind-v1-meta"><code>meta/v1.GroupVersionKind</code></a> </del> <ins> <a href="https://pkg.go.dev/k8s.io/apimachinery/pkg/apis/meta/v1#GroupVersionKind"><code>meta/v1.GroupVersionKind</code></a> </ins> </td> <td> <p>Kind is the fully-qualified type of object being submitted (for example, v1.Pod or autoscaling.v1.Scale)</p> </td> </tr> <tr><td><code>resource</code> <B>[Required]</B><br/> <del> <a href="https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.27/#groupversionresource-v1-meta"><code>meta/v1.GroupVersionResource</code></a> </del> <ins> <a href="https://pkg.go.dev/k8s.io/apimachinery/pkg/apis/meta/v1#GroupVersionResource"><code>meta/v1.GroupVersionResource</code></a> </ins> </td> <td> <p>Resource is the fully-qualified resource being requested (for example, v1.pods)</p>

</td> </tr> <tr><td><code>requestKind</code><br/> <del> <a href="https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.27/#groupversionkind-v1-meta"><code>meta/v1.GroupVersionKind</code></a> </del> <ins> <a href="https://pkg.go.dev/k8s.io/apimachinery/pkg/apis/meta/v1#GroupVersionKind"><code>meta/v1.GroupVersionKind</code></a> </ins> </td> <td> <p>RequestKind is the fully-qualified type of the original API request (for example, v1.Pod or autoscaling.v1.Scale).

</td> </tr> <tr><td><code>requestResource</code><br/> <del> <a href="https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.27/#groupversionresource-v1-meta"><code>meta/v1.GroupVersionResource</code></a> </del> <ins> <a href="https://pkg.go.dev/k8s.io/apimachinery/pkg/apis/meta/v1#GroupVersionResource"><code>meta/v1.GroupVersionResource</code></a> </ins> </td> <td> <p>RequestResource is the fully-qualified resource of the original API request (for example, v1.pods).

</td> </tr> <tr><td><code>userInfo</code> <B>[Required]</B><br/> <del> <a href="https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.27/#userinfo-v1-authentication"><code>authentication/v1.UserInfo</code></a> </del> <ins> <a href="https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.27/#userinfo-v1-authentication-k8s-io"><code>authentication/v1.UserInfo</code></a> </ins> </td> <td> <p>UserInfo is information about the requesting user</p>
Change:
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 outdated descriptions in Why is this needed fix missing link to /releases update events Comments <!-- Any additional related comments that might help. Drawings/mockups would be extremely helpful (if required). --/language ja /assign
/triage accepted

Discussion:
Kubernetesはオープンソースなので、オンプレミスやパブリッククラウド、それらのハイブリッドなどの利点を自由に得ることができ、簡単に移行することができます。 <ins> Kubernetesをダウンロードするには、[ダウンロード](/releases/download/)セクションを訪れてください。 </ins> {{% /blocks/feature %}} {{< /blocks/section >}}

<button id="desktopShowVideoButton" onclick="kub.showVideo()">ビデオを見る</button> <br> <br> <del> <a href="https://events.linuxfoundation.org/kubecon-cloudnativecon-europe/?utm_source=kubernetes.io&utm_medium=nav&utm_campaign=kccnceu22" button id="desktopKCButton">2022年5月16日〜20日のKubeCon EUバーチャルに参加する</a> </del> <ins> <a href="https://events.linuxfoundation.org/kubecon-cloudnativecon-europe/" button id="desktopKCButton">2023年4月18日〜21日のKubeCon + CloudNativeCon Europeに参加する</a> </ins> <br> <br> <br> <br> <del> <a href="https://events.linuxfoundation.org/kubecon-cloudnativecon-north-america/?utm_source=kubernetes.io&utm_medium=nav&utm_campaign=kccncna22" button id="desktopKCButton">2022年10月24日-28日のKubeCon NAバーチャルに参加する</a> </del> <ins> <a href="https://events.linuxfoundation.org/kubecon-cloudnativecon-north-america/" button id="desktopKCButton">2023年11月6日〜9日のKubeCon + CloudNativeCon North Americaに参加する</a> </ins> </div> <div id="videoPlayer"> <iframe data-url="https://www.youtube.com/embed/H06qrNmGqyE?autoplay=1" frameborder="0" allowfullscreen></iframe>
Change:
This example... has an issue. dig always returns true "0" regardless of whether the name resolves, so if the intent is that 'dig myservice' should be replaced with the dns name of the services this will always loop to 100 and end. perhaps this should be: will filter NXDOMAIN (failing DNS)
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
Ref Link : /sig docs /language en
I agree with you about this modification of command. the script will exit successfully when it detects a failed DNS resolution (NXDOMAIN)
/kind support
/remove-kind support
Agree that the always returns true "0" regardless of whether the service exists. But the scenario is . The still does not work, because If the does not exist, the command returns 0, and the script exits 0. We can not wait for the service. To wait for the service to be created, we can replace with since "nslookup returns with an exit status of 1 if any query failed, and 0 otherwise."
Thanks abel8! nslookup is better with its exit behavior. And the example reads cleaner without the extra pipe and complexity. Nice! Thanks!
you had raised the PR to fix the issue so you can assign this issue to yourself. /assign

Discussion:
* Wait for a {{< glossary_tooltip text="Service" term_id="service">}} to be created, using a shell one-line command like: ```shell <del> for i in {1..100}; do sleep 1; if dig myservice; then exit 0; fi; done; exit 1 </del> <ins> for i in {1..100}; do sleep 1; if nslookup myservice; then exit 0; fi; done; exit 1 </ins> ``` * Register this Pod with a remote server from the downward API with a command like:
Change:
This is a Bug Report Problem: The link for under is wrong. It is redirected to the instead of that it should redirect to the . It is due to the following PR: Proposed Solution: It should redirect to instead of Page to Update:
/assign /sig docs
/retitle Incorrect link for Service Proxies /language en /triage accepted /priority backlog
Fixed it here:

Discussion:
`attach` and `port-forward` requests. - `SupportIPVSProxyMode`: Enable providing in-cluster service load balancing using IPVS. <del> See [service proxies](/docs/concepts/services-networking/service/#virtual-ips-and-service-proxies) for more details. </del> <ins> See [service proxies](/docs/reference/networking/virtual-ips/) for more details. </ins> - `SupportNodePidsLimit`: Enable the support to limiting PIDs on the Node.  The parameter `pid=<number>` in the `--system-reserved` and `--kube-reserved` options can be specified to
Change:
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.

Discussion:
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:
Change:
This is a Bug Report Problem: The FEATURE STATE of the following features is mentioned wrongly(outdated) under the docs: : The corresponding feature gate is and mentioned Feature State is : The corresponding feature gate is and mentioned Feature State is Proposed Solution: According to the docs, for Feature State should be and for Feature State should be Page to Update:
/language en /sig docs /sig network
/assign
Fixed it here:
/retitle Feature gates and incorrectly marked as beta
/triage accepted

Discussion:
#### IP address ranges for Service virtual IP addresses {#service-ip-static-sub-range} <del> {{< feature-state for_k8s_version="v1.25" state="beta" >}} </del> <ins> {{< feature-state for_k8s_version="v1.26" state="stable" >}} </ins> Kubernetes divides the `ClusterIP` range into two bands, based on the size of the configured `service-cluster-ip-range` by using the following formula

### Internal traffic policy <del> {{< feature-state for_k8s_version="v1.22" state="beta" >}} </del> <ins> {{< feature-state for_k8s_version="v1.26" state="stable" >}} </ins> You can set the `.spec.internalTrafficPolicy` field to control how traffic from internal sources is routed. Valid values are `Cluster` and `Local`. Set the field to
Change:
When starting kubelet with the provided unit file in , kubelet crashes, stating that all of the specified flags are either deprecated or completely unknown: If this service file is no longer valid, the documentation should not include it.
/language en /kind support
it seems kubeadm and kubernete versions are mismatching. In kubernetes v1-27, the --container-runtime flag has been removed. ref:
there is an open pr to cleanup the removed flag just remove it to continue your setup. there is no plan to remove the other deprecated kubelet flags anytime soon because they are widely used. in the example we can use a kubeletconfiguration instead. pr welcome to change the example to use --config. /priority backlog /triage accepted /sig cluster-lifecycle
/retitle migrate deprecated flags to config in kubeadm HA etcd page
steps edit this section change the example to this /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 : steps </details
/assign
Raised PR, please confirm the changes.

Discussion:
that has higher precedence than the kubeadm-provided kubelet unit file. ```sh <ins> cat << EOF > /etc/systemd/system/kubelet.service.d/kubelet.conf # Replace "systemd" with the cgroup driver of your container runtime. The default value in the kubelet is "cgroupfs". # Replace the value of "containerRuntimeEndpoint" for a different container runtime if needed. # apiVersion: kubelet.config.k8s.io/v1beta1 kind: KubeletConfiguration cgroupDriver: systemd address: 127.0.0.1 containerRuntimeEndpoint: unix:///var/run/containerd/containerd.sock staticPodPath: /etc/kubernetes/manifests EOF </ins> cat << EOF > /etc/systemd/system/kubelet.service.d/20-etcd-service-manager.conf [Service] ExecStart= <del> # Replace "systemd" with the cgroup driver of your container runtime. The default value in the kubelet is "cgroupfs". # Replace the value of "--container-runtime-endpoint" for a different container runtime if needed. ExecStart=/usr/bin/kubelet --address=127.0.0.1 --pod-manifest-path=/etc/kubernetes/manifests --cgroup-driver=systemd --container-runtime-endpoint=unix:///var/run/containerd/containerd.sock </del> <ins> ExecStart=/usr/bin/kubelet --config=/etc/systemd/system/kubelet.service.d/kubelet.conf </ins> Restart=always EOF
Change:
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

Discussion:
Để 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 một phiên bản cụ thể. <del> Ví dụ như, để tải về phiên bản {{< param "fullversion" >}} trên Linux, hãy nhập như sau: </del> <ins> Ví dụ như, để tải về phiên bản {{< skew currentPatchVersion >}} trên Linux, hãy nhập như sau: </ins> ``` <del> curl -LO https://dl.k8s.io/release/{{< param "fullversion" >}}/bin/linux/amd64/kubectl </del> <ins> curl -LO https://dl.k8s.io/release/v{{< skew currentPatchVersion >}}/bin/linux/amd64/kubectl </ins> ``` 2. Tạo kubectl binary thực thi.

Để 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.

### Cài đặt kubectl binary với curl trên Windows <del> 1. Tải về phiên bản mới nhất {{< param "fullversion" >}} từ [đường dẫn này](https://dl.k8s.io/release/{{< param "fullversion" >}}/bin/windows/amd64/kubectl.exe). </del> <ins> 1. Tải về phiên bản mới nhất {{< skew currentPatchVersion >}} từ [đường dẫn này](https://dl.k8s.io/release/v{{< skew currentPatchVersion >}}/bin/windows/amd64/kubectl.exe). </ins> Hoặc nếu bạn đã cài đặt `curl`, hãy sử dụng câu lệnh sau: ``` <del> curl -LO https://dl.k8s.io/release/{{< param "fullversion" >}}/bin/windows/amd64/kubectl.exe </del> <ins> curl -LO https://dl.k8s.io/release/v{{< skew currentPatchVersion >}}/bin/windows/amd64/kubectl.exe </ins> ``` Để tìm ra phiên bản ổn định mới nhất, hãy xem [https://dl.k8s.io/release/stable.txt](https://dl.k8s.io/release/stable.txt).
Change:
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. --We need to update some links in because these links are broken. True) False) True) False) Why is this needed These links are broken. Comments <!-- Any additional related comments that might help. Drawings/mockups would be extremely helpful (if required). --/language ja /assign
About aggregator - is certainly correct, but we would like to match the English page first. You already did so in PR .
Thank you for your advice! The URL listed in the Issue was incorrect and has been corrected. As you said, PR already uses this URL.
/triage accepted

Discussion:
## APIグループ <del> [API groups](https://git.k8s.io/community/contributors/design-proposals/api-machinery/api-group.md)で、KubernetesのAPIを簡単に拡張することができます。 </del> <ins> [API groups](https://git.k8s.io/design-proposals-archive/api-machinery/api-group.md)で、KubernetesのAPIを簡単に拡張することができます。 </ins> APIグループは、RESTパスとシリアル化されたオブジェクトの`apiVersion`フィールドで指定されます。 KubernetesにはいくつかのAPIグループがあります:

## {{% heading "whatsnext" %}} - [API conventions](https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#api-conventions)をもっと知る <del> - [aggregator](https://github.com/kubernetes/community/blob/master/contributors/design-proposals/api-machinery/aggregated-api-servers.md)の設計ドキュメントを読む </del> <ins> - [aggregator](https://git.k8s.io/design-proposals-archive/api-machinery/aggregated-api-servers.md)の設計ドキュメントを読む </ins>
Change:
This is a Bug Report <!--Required Information--Problem: The Japanese documentation does not apply a redirect from Getting Started Learning Environment to Tasks Tools. Without this redirection, there will be inconsistencies in information access compared to the English documentation Proposed Solution: Add a redirect from to Page to Update: Additional Information: /language ja /assign
This Issue seems to point out the differences between EN and JP. On the EN page, When we click on "Getting started" - "Learning environment" in the Left-sidebar, it will jump to docs/tasks/tools/. On the JP page, When we click on the same item in the Left-sidebar, it does not jump to docs/tasks/tools/.
It's a helpful clarification!
/triage accepted
/kind bug /remove-kind feature
I think this issues is related to bug, not feature. So could you update the description?
I have updated the description to reflect the issue as a bug.

Discussion:
/docs/setup/learning-environment/     /docs/tasks/tools/  302! /id/docs/setup/learning-environment/     /id/docs/tasks/tools/  302! /zh-cn/docs/setup/learning-environment/     /zh-cn/docs/tasks/tools/  302! <ins> /ja/docs/setup/learning-environment/     /ja/docs/tasks/tools/  302! </ins> /hi/docs/setup/learning-environment/     /hi/docs/tasks/tools/ 302! /docs/setup/learning-environment/kind/  /docs/tasks/tools/  302 /id/docs/setup/learning-environment/kind/  /id/docs/tasks/tools/  302
Change:
It looks like the feature gate "NamespaceDefaultLabelName" has been removed as described on this page: But it's noted on this page that it can be enabled: Maybe that the "Namespaces" page needs to be updated.
/language en /sig docs
/retitle Unclear documentation on feature gate The documentation is not wrong; however, we can clean up to avoid mentioning the feature gate at all (we'd keep the feature-state shortcode). /priority backlog /help /triage accepted
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 : /retitle Unclear documentation on feature gate to avoid mentioning the feature gate at all (we'd keep the feature-state shortcode). /help /triage accepted 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
I had the same doubts before, and I changed it by the way, please help review, thanks

Discussion:
{{< feature-state for_k8s_version="1.22" state="stable" >}} The Kubernetes control plane sets an immutable {{< glossary_tooltip text="label" term_id="label" >}} <del> `kubernetes.io/metadata.name` on all namespaces, provided that the `NamespaceDefaultLabelName` [feature gate](/docs/reference/command-line-tools-reference/feature-gates/) is enabled. </del> <ins> `kubernetes.io/metadata.name` on all namespaces. </ins> The value of the label is the namespace name.
Change:
This is a Bug Report Problem: Links for Avoiding collisions are broken in: (at point) Proposed Solution: Update in both pages with Other possible solutions: Page to Update:
/language en /area blog
/retitle Broken links for "Avoiding collisions" in 'Service' and 'Feature Gates' page /remove-area blog
I think the link became broken during the revision process of the Service concept page. We should make an update to direct it to the correct location, which I believe is /priority backlog /triage accepted
/assign
/sig docs PR raised
Similar to

Discussion:
If you try to create a Service with an invalid `clusterIP` address value, the API server will return a 422 HTTP status code to indicate that there's a problem. <del> Read [avoiding collisions](#avoiding-collisions) </del> <ins> Read [avoiding collisions](/docs/reference/networking/virtual-ips/#avoiding-collisions) </ins> to learn how Kubernetes helps reduce the risk and impact of two different Services both trying to use the same IP address.

ClusterIP range is subdivided. Dynamic allocated ClusterIP addresses will be allocated preferently from the upper range allowing users to assign static ClusterIPs from the lower range with a low risk of collision. See <del> [Avoiding collisions](/docs/concepts/services-networking/service/#avoiding-collisions) </del> <ins> [Avoiding collisions](/docs/reference/networking/virtual-ips/#avoiding-collisions) </ins> for more details. - `SizeMemoryBackedVolumes`: Enable kubelets to determine the size limit for memory-backed volumes (mainly `emptyDir` volumes).