jiebi/CodeConvo huggingface dataset:
Change:
1. When dual-stack is enabled on a cluster, existing Services (whether `IPv4` or `IPv6`) are configured by the control plane to set `.spec.ipFamilyPolicy` to `SingleStack` and set `.spec.ipFamilies` to the address family of the existing Service. The existing Service cluster IP <del> will be stored in `.spec.ClusterIPs`. </del> <ins> will be stored in `.spec.clusterIPs`. </ins> {{% code_sample file="service/networking/dual-stack-default-svc.yaml" %}}

Discussion:
page is plenty of wrong references to the non defined ` instead.
/triage accepted
/good-first-issue
This request has been marked as suitable for new contributors. Please ensure that the issue body includes answers to the following questions: Why are we solving this issue? To address this issue, are there any code changes? If there are code changes, what needs to be done in the code and what places can the assignee treat as reference points? Does this issue have zero to low barrier of entry? How can the assignee reach out to you for help? For more details on the requirements of such an issue, please see and ensure that they are met. If this request no longer meets these requirements, the label can be removed by commenting with the command. <detailsIn response to : /good-first-issue Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details
/kind bug
/assign
Thanks for solving this so so quick (you are the best ;-)
Change:
spans for 1 in 10000 requests, and uses the default OpenTelemetry endpoint: ```yaml <del> apiVersion: apiserver.config.k8s.io/v1beta1 </del> <ins> apiVersion: apiserver.config.k8s.io/v1alpha1 </ins> kind: TracingConfiguration # default value #endpoint: localhost:4317

Discussion:
Hi, this page has a link which is 404, but I can't find this page in kubernetes website.
In this PR the page: has been removed. should point to the latest page link: /assign
/triage accepted
I could not find the description in the latest page link Is that missing?
Yes, I also checked this struct just now, it doesn't exist in the This struct was removed in version v1. Not sure about the upgrade status of this struct. /cc
There were some nits in the reference generator. We are fixing them and then regenerate the references.
TracingConfiguration is still alpha, and thus doesn't exist in the v1 version of the API.
/kind bug /language en
So do we need to create a new page containing the TracingConfiguration struct so that we can link to it? Or link to the kubernetes TracingConfiguration code line: Which one do you prefer or have a better suggestion?
I'll create a PR updating the config APIs. As for the TracingConfiguration type, it is only part of the v1alpha1 version. This means the current code is incorrect and the v1alpha1 reference needs to be back. This warrants a separate PR.
First PR created
Second PR created /assign
Change:
chmod +x kubectl mkdir -p ~/.local/bin/kubectl mv ./kubectl ~/.local/bin/kubectl <del> # and then add ~/.local/bin/kubectl to $PATH </del> <ins> # and then append (or prepend) ~/.local/bin to $PATH </ins> ``` {{< /note >}}

Discussion:
Hello, I have recently and I have noticed that there is a slight error at step 3. Namely, the line says: when it really should be: I have tested it a few times and indeed, adding to PATH does not work, while simply adding yields the correct result (i.e. being able to invoke kubectl commands from the command prompt). I know it is a minor issue but for beginners (like myself) it could make the difference between completing the installation or not. Even though I have not tried other methods of installation, I suspect that the same step should also be corrected in section , where it also says "Add the binary in to your PATH." Best regards, Paula
/triage accepted Similar issue exists in . cf. In : !
is kind of techie vernacular (it's how I'd say it in spoken English to a colleague), but in technical docs we can be more precise. /language en
Hi, I would like to work on this issue. /assign
/sig windows
Change:
## Start a Kubelet process configured via the config file {{< note >}} <del> If you use kubeadm to initialize your cluster, use the kubelet-config while creating your cluster with `kubeadmin init`. </del> <ins> If you use kubeadm to initialize your cluster, use the kubelet-config while creating your cluster with `kubeadm init`. </ins> See [configuring kubelet using kubeadm](/docs/setup/production-environment/tools/kubeadm/kubelet-integration/) for details. {{< /note >}}

Discussion:
reference:
/assign
/assign
hello, can you please leave this this will be my first contributions towards open source. hope you don't mind.
Sure
/unassign
/triage accepted
/kind documentation
Change:
{{< note >}} <del> * You must create a [ConfigMap](/docs/tasks/configure-pod-container/configure-pod-configmap/) </del> <ins> * You must [create a ConfigMap](/docs/tasks/configure-pod-container/configure-pod-configmap/#create-a-configmap) </ins> before you can use it. * A ConfigMap is always mounted as `readOnly`.

Discussion:
This is a Bug Report Problem: The link for under in is incorrect. It is redirecting to instead of that it should redirect to Proposed Solution: Create a ConfigMap should redirect to instead of .
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
Page related to the issue:
/language en /sig docs
I would like to work on this issue if triage gets accepted.
The issue is fixed
Change:
margin: 0 auto; } <ins> .content .quote-text p { color: #fff; font-size: 100%; line-height: 1.4em; margin-bottom: 0; } </ins> .quote-author { display: block; margin-top: 3em;

Discussion:
This is a clean up request <!-- Please only use this template for submitting feature/enhancement requests --<!-- See for guidance on writing an actionable issue description. --What would you like to be Update the to use the  shortcode that is built in to Hugo. Why is this needed Using HTML and s directly is not as easy to maintain as Hugo shortcodes, which are explicitly designed to afford code reuse. Comments /kind cleanup /help /language en If you make this change, and check that the videos still render. Related to
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 : This is a clean up request <!-- See for guidance on writing an actionable issue description. --Update the to use the  shortcode that is built in to Hugo. Using HTML and s directly is not as easy to maintain as Hugo shortcodes, which are explicitly designed to afford code reuse. /kind cleanup /help /language en 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
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
/assign
Thanks
Change:
2. Assign the PR to one or more current SIG Docs approvers. <del> If approved, a SIG Docs lead adds you to the appropriate GitHub team. Once added, [K8s-ci-robot](https://github.com/kubernetes/test-infra/tree/master/prow#bots-home) assigns and suggests you as a reviewer on new pull requests. </del>  No newline at end of file <ins> If approved, a SIG Docs lead adds you to the appropriate GitHub team. Once added, [@k8s-ci-robot](https://github.com/kubernetes/test-infra/tree/master/prow#bots-home) assigns and suggests you as a reviewer on new pull requests. ## {{% heading "whatsnext" %}} - Read about [PR wrangling](/docs/contribute/participating/pr-wranglers), a role all approvers take on rotation. </ins>  No newline at end of file

Discussion:
Umbrella issue: Take Advanced Contributing Be a PR Wrangler for a week topic and create a new page, Participating in SIG Docs PR Wranglers.
/assign /kind cleanup
/language en
Change:
레플리카셋이 새로운 파드를 생성해야 할 경우, 명시된 파드 템플릿을 사용한다. <del> 레플리카셋은 파드의 [metadata.ownerReferences](/ko/docs/concepts/workloads/controllers/garbage-collection/#소유자-owner-와-종속-dependent) </del> <ins> 레플리카셋은 파드의 [metadata.ownerReferences](/ko/docs/concepts/architecture/garbage-collection/#소유자-owner-와-종속-dependent) </ins> 필드를 통해 파드에 연결되며, 이는 현재 오브젝트가 소유한 리소스를 명시한다. 레플리카셋이 가지고 있는 모든 파드의 ownerReferences 필드는 해당 파드를 소유한 레플리카셋을 식별하기 위한 소유자 정보를 가진다. 이 링크를 통해 레플리카셋은 자신이 유지하는 파드의 상태를 확인하고 이에 따라 관리 한다.

Discussion:
This is a Feature Request Translate in Korean What would you like to be Translate in Korean Why is this needed This file is not translated yet. Comments Page to translate : /language ko /assign Comments <!-- Any additional related comments that might help. Drawings/mockups would be extremely helpful (if required). --
/triage accepted
Resolved by page: /close
Closing this issue. <detailsIn response to : Resolved by 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:
Kubernetesクラスターが必要、かつそのクラスターと通信するためにkubectlコマンドラインツールが設定されている必要があります。 <del> まだクラスターがない場合、[Minikube](/ja/docs/setup/learning-environment/minikube/)を使って作成するか、 </del> <ins> このチュートリアルは、コントロールプレーンのホストとして動作していない少なくとも2つのノードを持つクラスターで実行することをおすすめします。 まだクラスターがない場合、[minikube](https://minikube.sigs.k8s.io/docs/tutorials/multi_node/)を使って作成するか、 </ins> 以下のいずれかのKubernetesプレイグラウンドも使用できます: * [Katacoda](https://www.katacoda.com/courses/kubernetes/playground)

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. --Translate into Japanese Why is this needed This page has not been translated. Comments <!-- Any additional related comments that might help. Drawings/mockups would be extremely helpful (if required). --/language ja /assign /triage accepted
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-contributor-experience at . /lifecycle stale
Change:
title: "zsh auto-completion" description: "Some optional configuration for zsh auto-completion." headless: true <ins> _build: list: never render: never publishResources: false </ins> --- The kubectl completion script for Zsh can be generated with the command `kubectl completion zsh`. Sourcing the completion script in your shell enables kubectl autocompletion.

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 source Markdown needs to exist for pages such as but we don't need to make those turn into actual web pages. Proposed Solution: Edit every file within : Page to Update: and its contents /area web-development /help /priority backlog /good-first-issue
This request has been marked as suitable for new contributors. Please ensure that the issue body includes answers to the following questions: Why are we solving this issue? To address this issue, are there any code changes? If there are code changes, what needs to be done in the code and what places can the assignee treat as reference points? Does this issue have zero to low barrier of entry? How can the assignee reach out to you for help? For more details on the requirements of such an issue, please see and ensure that they are met. If this request no longer meets these requirements, the label can be removed by commenting with the command. <detailsIn response to : This is a Bug Report <!-- See for guidance on writing an actionable issue description. --Problem: The source Markdown needs to exist for pages such as but we don't need to make those turn into actual web pages. Edit every file within : Page to Update: and its contents /help /priority backlog /good-first-issue </details
/retitle Include files for install are rendered and served /triage accepted
/assign
/unassign
Thanks !
Change:
/docs/tutorials/kubernetes-basics/expose-intro/     /docs/tutorials/kubernetes-basics/expose/expose-intro/ 301 /docs/tutorials/kubernetes-basics/scale-interactive/     /docs/tutorials/kubernetes-basics/scale/scale-interactive/ 301 /docs/tutorials/kubernetes-basics/scale-intro/     /docs/tutorials/kubernetes-basics/scale/scale-intro/ 301 <ins> /docs/tutorials/clusters/apparmor/     /docs/tutorials/security/apparmor/   301 /docs/tutorials/clusters/seccomp/      /docs/tutorials/security/seccomp/    301 </ins> /ja/docs/tutorials/kubernetes-basics/scale-intro/     /ja/docs/tutorials/kubernetes-basics/scale/scale-intro/ 301 /ko/docs/tutorials/kubernetes-basics/scale-intro/     /ko/docs/tutorials/kubernetes-basics/scale/scale-intro/ 301 /docs/tutorials/kubernetes-basics/update-interactive/    /docs/tutorials/kubernetes-basics/update/update-interactive/ 301

Discussion:
This is a Feature Request What would you like to be Post-merge of , move the tutorials under into Merge clusters section into security section here: Why is this needed Issue description is a slight modification from original request in the comment Comments /hold for /cc /sig docs security
this might be a good first issue for new contributors in sig-security-docs /triage accepted
Hi, I would like to work on this issue. /assign
/kind cleanup
Hi , I a query: moving the tutorials from the cluster sub-directory into the security sub-directory, the cluster sub-directory will only have its file so do I need to do something regarding it ( file)? Thanks
Whenever you are free can you please help me with the above mentioned query. Thanks
Change:
</ul> <h2>Basics</h2> <p>The preferred way to configure kubeadm is to pass an YAML configuration file with <del> the `--config“ option. Some of the configuration options defined in the kubeadm </del> <ins> the <code>--config</code> option. Some of the configuration options defined in the kubeadm </ins> config file are also available as command line flags, but only the most common/simple use case are supported with this approach.</p> <p>A kubeadm config file could contain multiple configuration types separated using three dashes (<code>---</code>).</p>

Discussion:
The indentation of the example configuration is messy. !
/kind bug /language en page:
Also Consider to remove the exist in the same page under . Note: This page is automatically generated, you are not allowed to directly change the documentation page.
/retitle Messy indentation on kubeadm config reference page
/priority backlog We'd prioritize other improvements over this one. /triage accepted
/assign This is because the Golang source code contains TAB characters instead of SPACEs as a convention, and those TABs are messing up the YAML snippet. I'll work on this.
PR sent for website. PR sent for the generator.
Change:
Failed | Failed | 파드의 상태에 한함 Federation | 페더레이션 | field | 필드 | <del> Flannel | Flannel | </del> <ins> Flannel | 플란넬(Flannel) | </ins> form | 형식 | Google Compute Engine | Google Compute Engine | hash | 해시 |

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. --There are several CNI plugins that need to be translated into Korean to be to . English --- --- Calico Cilium Flannel Kube-router Romana Weave-net Weaveworks 'Weave Net' . Why is this needed This is for standardization of terminology when document is localized. Comments <!-- Any additional related comments that might help. Drawings/mockups would be extremely helpful (if required). --Page to update: - /language ko
/assign
Change:
## What Kubernetes is not <del> Kubernetes is not a traditional, all-inclusive PaaS (Platform as a Service) system. Since Kubernetes operates at the container level rather than at the hardware level, it provides some generally applicable features common to PaaS offerings, such as deployment, scaling, load balancing, logging, and monitoring. However, Kubernetes is not monolithic, and these default solutions are optional and pluggable. Kubernetes provides the building blocks for building developer platforms, but preserves user choice and flexibility where it is important. </del> <ins> Kubernetes is not a traditional, all-inclusive PaaS (Platform as a Service) system. Since Kubernetes operates at the container level rather than at the hardware level, it provides some generally applicable features common to PaaS offerings, such as deployment, scaling, load balancing, and lets users integrate their logging, monitoring, and alerting solutions. However, Kubernetes is not monolithic, and these default solutions are optional and pluggable. Kubernetes provides the building blocks for building developer platforms, but preserves user choice and flexibility where it is important. </ins> 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: The paragraph: The line is confusing at the page goes on to say later that K8S does not provide these solutions. Proposed Solution: I would suggest that the line be modified to be clear that . rather than saying that it provides those features. It is easier to understand for novice learners who are just getting started with K8S. Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--
That sounds like a good clarification /kind cleanup /language en /priority awaiting-more-evidence
/assign
Change:
documentation for [deleting Pods from a StatefulSet](/docs/tasks/run-application/force-delete-stateful-set-pod/). <ins> ### Pod shutdown and sidecar containers {##termination-with-sidecars} If your Pod includes one or more [sidecar containers](/docs/concepts/workloads/pods/sidecar-containers/) (init containers with an Always restart policy), the kubelet will delay sending the TERM signal to these sidecar containers until the last main container has fully terminated. The sidecar containers will be terminated in the reverse order they are defined in the Pod spec. This ensures that sidecar containers continue serving the other containers in the Pod until they are no longer needed. This means that slow termination of a main container will also delay the termination of the sidecar containers. If the grace period expires before the termination process is complete, the Pod may enter [forced termination](#pod-termination-beyond-grace-period). In this case, all remaining containers in the Pod will be terminated simultaneously with a short grace period. Similarly, if the Pod has a `preStop` hook that exceeds the termination grace period, emergency termination may occur. In general, if you have used `preStop` hooks to control the termination order without sidecar containers, you can now remove them and allow the kubelet to manage sidecar termination automatically. </ins> ### Garbage collection of Pods {#pod-garbage-collection} For failed Pods, the API objects remain in the cluster's API until a human or

Discussion:
work not well. Not sure how to fix it. This issue has spreaded to the currently. <img width="550" alt="image" src=""
/triage accepted
/language en
For a likely fix, see
Change:
* EndpointSlice controller: Populates EndpointSlice objects (to provide a link between Services and Pods). * ServiceAccount controller: Create default ServiceAccounts for new namespaces. <ins> The above is not an exhaustive list. </ins> ### cloud-controller-manager {{< glossary_definition term_id="cloud-controller-manager" length="short" >}}

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. --I think adding some expressions to indicate controller manager runs many controllers explicitly, moreover indicate the actual amount of controllers in document page is useful for beginner. Why is this needed When I communicated with some k8s beginners, they think controller-manager only run 4 controllers refered to the document. Actually controller manager has run nearly 40 controllers currently, and the amount will increase in the future in predict. Comments <!-- Any additional related comments that might help. Drawings/mockups would be extremely helpful (if required). --
Its difficult to mention all the controllers in the document as some examples of the controllers that run within the kube-controller-manager process. There are additional controllers for different aspects of the Kubernetes cluster.
/language en Rather we can say there are more controllers that run within the kube-controller-manager. With few more examples
/triage accepted /priority backlog Don't add more examples. Instead, reword to make it clearer that the 4 examples listed are selected from a much larger set.
Expression in is puzzled too
There I would make changes. Swap: remove “replication controller” out, using “statefulset controller” as its replacement remove “endpoints controller” out, using “endpointslice controller” as its replacement
/good-first-issue
This request has been marked as suitable for new contributors. Please ensure that the issue body includes answers to the following questions: Why are we solving this issue? To address this issue, are there any code changes? If there are code changes, what needs to be done in the code and what places can the assignee treat as reference points? Does this issue have zero to low barrier of entry? How can the assignee reach out to you for help? For more details on the requirements of such an issue, please see and ensure that they are met. If this request no longer meets these requirements, the label can be removed by commenting with the command. <detailsIn response to : /good-first-issue Instructions for interacting with me using PR comments are available .

If you have questions or suggestions related to my behavior, please file an issue against the repository. </details
I'd like to work on this
/assign
/assign
Hey has assigned this issue already. You can find another issue that you can work on.