jiebi/CodeConvo huggingface dataset:
Change:
title: 코드 컨트리뷰터(Code Contributor) id: code-contributor date: 2018-04-12 <del> full_link: /ko/docs/community/devel/ </del> <ins> full_link: https://github.com/kubernetes/community/tree/master/contributors/devel </ins> short_description: > 쿠버네티스 오픈소스 코드베이스에 코드를 개발하고 기여하는 사람.

Discussion:
This is a Feature Request Korean Localization for branch. What would you like to be Any localization contributions for Korean. Comments This issue is to notify the schedule of Korean localization to contributors. is the current work branch for Korean localization. Important dates A Korean localization work branch is merged to main branch after we complete around 3~4 weeks job. PR Freeze: 10/03 (PR opened after freeze will be requested to rebase to next work branch) Branch Merge: 10/06 (merge to main branch) 3~4 , main . PR : 10/03 ( PR , PR ) : 10/06 (main , k8s.io ) /language ko /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 : ## In English This is a Feature Request is the current work branch for Korean localization.PR Freeze: 10/03 (PR opened after freeze will be requested to rebase to next work branch) Branch Merge: 10/06 (merge to main branch) PR : 10/03 ( PR , PR ) : 10/06 (main , k8s.io ) /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
Thanks :) /triage accepted
/milestone dev-1.25-ko.1
Change:
Type    Reason            Age   From            Message ----    ------            ----  ----            ------- Normal  SuccessfulCreate  14m   job-controller  Created pod: pi-5rwd7 <del> ``` </del> <ins> {{< /tab >}} {{< tab name="kubectl get job pi -o yaml" codelang="bash" >}} apiVersion: batch/v1 kind: Job metadata: annotations: kubectl.kubernetes.io/last-applied-configuration: | {"apiVersion":"batch/v1","kind":"Job","metadata":{"annotations":{},"name":"pi","namespace":"default"},"spec":{"backoffLimit":4,"template":{"spec":{"containers":[{"command":["perl","-Mbignum=bpi","-wle","print bpi(2000)"],"image":"perl","name":"pi"}],"restartPolicy":"Never"}}}} creationTimestamp: "2022-06-15T08:40:15Z" generation: 1 labels: controller-uid: 863452e6-270d-420e-9b94-53a54146c223 job-name: pi name: pi namespace: default resourceVersion: "987" uid: 863452e6-270d-420e-9b94-53a54146c223 spec: backoffLimit: 4 completionMode: NonIndexed completions: 1 parallelism: 1 selector: matchLabels: controller-uid: 863452e6-270d-420e-9b94-53a54146c223 suspend: false template: metadata: creationTimestamp: null labels: controller-uid: 863452e6-270d-420e-9b94-53a54146c223 job-name: pi spec: containers: - command: - perl - -Mbignum=bpi - -wle - print bpi(2000) image: perl imagePullPolicy: Always name: pi resources: {} terminationMessagePath: /dev/termination-log terminationMessagePolicy: File dnsPolicy: ClusterFirst restartPolicy: Never schedulerName: default-scheduler securityContext: {} terminationGracePeriodSeconds: 30 status: active: 1 ready: 1 startTime: "2022-06-15T08:40:15Z" {{< /tab >}} {{< /tabs >}} </ins> To view completed Pods of a Job, use `kubectl get pods`.

Discussion:
Why don't you just provide a completed example of a job with Labels, Parallelism, Completions instead of getting them from describing the job?
/kind feature /language en /priority backlog /triage accepted Nice suggestion. I don't suppose you'd be willing to open a pull request to make that change ? The source for that page is at
If I've understood what you were suggesting correctly, you would like to see what the of a Job looks like in the API. You (or anyone working on this improvement) could use to let the reader choose between using and (if you wanted examples of writing a spec for a parallel Job, then the section of that page has links to some examples already, and also links to the API reference for Job).
I would like to work on this. /assign
Change:
Here's an example configuration file: <del> {% include code.html language="yaml" file="simple_deployment.yaml" ghlink="/docs/concepts/tools/simple_deployment.yaml" %} </del> <ins> {% include code.html language="yaml" file="simple_deployment.yaml" ghlink="/docs/tutorials/object-management-kubectl/simple_deployment.yaml" %} </ins> Create the object using `kubectl apply`: ```shell <del> kubectl apply -f http://k8s.io/docs/concepts/tools/kubectl/simple_deployment.yaml </del> <ins> kubectl apply -f http://k8s.io/docs/tutorials/object-management-kubectl/simple_deployment.yaml </ins> ``` **Note:** For purposes of illustration, the preceding command refers to a single

Discussion:
<!-- Thanks for filing an issue! Before submitting, please fill in the following information. --<!--Required Information--This is a... <!-- choose one by changing [ ] to [x] --- [ ] Feature Request [x] Bug Report Problem: 404 on Proposed Solution: Update location of Page to Update:
Change:
spec: selector: matchLabels: <del> app: mysql-server </del> <ins> app: mysql </ins> app.kubernetes.io/name: mysql serviceName: mysql replicas: 3

Discussion:
I'm learning kubernetes and stepping through the various scenarios. I came across an issue that I can't tell if it is my own fault or some subtle issue with the yaml file. When I try to execute: kubectl apply -f After successfully doing the previous steps, I get: kubectl apply -f The StatefulSet "mysql" is invalid: Invalid value: map[string]string{"app":"mysql", "":"mysql"}: does not match template Should the mysql- be altered on line 15 (app: mysql) to match line 8 (app: mysql-server)? Or is there some other subtlety about label matching that will break how this app is structured? Thanks
HI , Edit your YAML files and set the same key-value pairs in both and
I am afraid to say that your suggestion is not a proper solution. If K8s doc has bug, then it would be great to fix that. This is reproducible for me. /triage accepted And rather than your suggestion ( L15 → ), I suggest this: [L8 in ] This will make the work.
I'd love to work on this /assign
Oops. This was introduced by - which I thought I'd fixed. Sorry about that.
Change:
To make a report, submit your vulnerability to the [Kubernetes bug bounty program](https://hackerone.com/kubernetes). This allows triage and handling of the vulnerability with standardized response times. <del> You can also email the private [security@kubernetes.io](mailto:security@kubernetes.io) list with the security details and the details expected for [all Kubernetes bug reports](https://git.k8s.io/kubernetes/.github/ISSUE_TEMPLATE/bug-report.md). </del> <ins> You can also email the private [security@kubernetes.io](mailto:security@kubernetes.io) list with the security details and the details expected for [all Kubernetes bug reports](https://github.com/kubernetes/kubernetes/blob/master/.github/ISSUE_TEMPLATE/bug-report.yaml). </ins> You may encrypt your email to this list using the GPG keys of the [Security Response Committee members](https://git.k8s.io/security/README.md#product-security-committee-psc). Encryption using GPG is NOT required to make a disclosure.

Discussion:
the is broken
Hello where did you find the link? And could you provide more details around where you intend to replace it?
Hi The link to the page is mentioned as the title of this issue. and the broken link (all Kubernetes bug reports) is under Correct link:
Thank you for providing the information.
/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
: Could you amend the body if the issue to reflect the above & confirm if you'll be working on the PR? If not, I'll have other contributors chip in
Hi I can't amend the body of the issue as I didn't create the issue. For the PR I'm up for it and will soon create a PR.
Hello could you please amend the body of the issue properly?
/assign
Fixed it here:
Change:
To customize kube-proxy you can pass a `KubeProxyConfiguration` next your `ClusterConfiguration` or `InitConfiguration` to `kubeadm init` separated by `---`. <del> For more details you can navigate to our [API reference pages](https://godoc.org/k8s.io/kubernetes/cmd/kubeadm/app/apis/kubeadm/v1beta3). </del> <ins> For more details you can navigate to our [API reference pages](/docs/reference/config-api/kubeadm-config.v1beta3/). </ins> --> ## 自定义 kube-proxy   {#customizing-kube-proxy}

Discussion:
!
/language zh /triage accepted
/kind bug
/assign
/retitle [zh] typo in kubeadm API
Change:
## Metrics (v1.30) <del> <!-- (auto-generated 2024 Apr 24) --> </del> <ins> <!-- (auto-generated 2024 Jul 02) --> </ins> <!-- (auto-generated v1.30) --> This page details the metrics that different Kubernetes components export. You can query the metrics endpoint for these components using an HTTP scrape, and fetch the current metrics data in Prometheus format.

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: removed metric from the documented metrics for Kubernetes v1.30, but the metric is still collected for the API server (ref: and ). Proposed Solution: Reinstate the documentation for such metric. Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--Kubernetes Version: v1.30 <!--Additional Information:--
/sig instrumentation
/triage accepted
This metrics exists in the file generated by . Or there is a problem with the file generated by before. Let me generate the metrics file again and see. /assign
After I re-ran the script, some metrics were indeed missing (not just metrics ), it was a problem with the generated script, I will take a closer look.
Change:
## Implementation notes <del> ![ha-master-gce](/images/docs/ha-master-gce.png) </del> <ins> ![ha-control-plane](/docs/images/ha-control-plane.svg) </ins> ### Overview <ins> The figure above illustrates three control plane nodes and their components in a highly available cluster. The control plane node’s components employ the following methods: - etcd: instances are clustered together using consensus. - Controllers, scheduler and cluster auto-scaler: only one instance of each will be active in a cluster using a lease mechanism. - Add-on manager: each works independently to keep add-ons in sync. In addition, a load balancer operating in front of the API servers routes external and internal traffic to the control plane nodes. </ins> Each of the control plane nodes will run the following components in the following mode: * etcd instance: all instances will be clustered together using consensus;

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 image in is in PNG format, which makes it hard for contributors to edit its content. Proposed Solution: Replace with SVG or something else (e.g. Google Drawings object, etc.) (Example of Google Drawings object: ) Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--/language en
/triage accepted We'd prefer SVG images, ideally with the text converted to shapes. It's OK to save an editable version somewhere else - SVG lets you add a comment about where to find the editable version.
I would like to work on this
/assign
fixing issue in Sorry for so many closed PRs, I'm newbie and got a little confused : )
Change:
If you want to change the Container Runtime on a Node from Docker Engine to containerd, you can find out more information on [migrating from Docker Engine to  containerd](/docs/tasks/administer-cluster/migrating-from-dockershim/change-runtime-containerd/), or, if you want to continue using Docker Engine in Kubernetes v1.24 and later, migrate to a <del> CRI-compatible adapter like [`cri-dockerd`](https://github.com/Mirantis/cri-dockerd). </del>  No newline at end of file <ins> CRI-compatible adapter like [`cri-dockerd`](https://github.com/Mirantis/cri-dockerd). </ins>

Discussion:
Documentation for external etcd cluster for kubernetes 1.27 is not up to date That the documentation doesn't take into consideration the fact that was removed in version 1.27 of kubelet: Restart=always Just try to install kubernetes with an external etcd cluster (which right now doesn't work anyway also for other reasons related to this ) with version 1.27.2 and you'll get: No response <details27.2 </details<detailsself-hosted </details<details</details<detailskubeadm </details<detailscontainerd </details<detailscalico </details
There are no sig labels on this issue. Please add an appropriate label by using one of the following commands: - Please see the for a listing of the SIGs, working groups, and committees available. <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
This issue is currently awaiting triage. If a SIG or subproject determines this is a relevant issue, they will accept it by applying the label and provide further guidance. 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
/transfer website /assign
removed the comment in v1.27. is not re-generated. I opened to fix it.
/retitle flag still in the documentation for external etcd in version 1.27 despite removal /language en /triage accepted
Change:
IP.1 = $ENV::WORKER_IP ``` <del> 2.  Generate the necessary TLS assets for this worker. This relies on the worker's IP address, and the `ca.pem` file generated earlier in the guide. </del> <ins> 2.  Generate the necessary TLS assets for this worker. This relies on the worker's IP address, and the `ca.pem` and `ca-key.pem` files generated earlier in the guide. </ins> ```shell # Export this worker's IP address.

Discussion:
Step 2 of says that it uses the generated earlier. In fact it also uses the ca- generated earlier.
Change:
kubectl-convert चेकसम फ़ाइल डाउनलोड करें: ```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/v{{< skew currentPatchVersion >}}/bin/windows/amd64/kubectl-convert.exe.sha256 </ins> ``` चेकसम फ़ाइल से kubectl-convert बाइनरी को मान्य करें:

Discussion:
Parent issue: Substitute the outdated shortcode with the new shortcode in the Hindi language documentation. /assign /triage accepted /language hi
PR has been raised to address this issue.
Change:
<ins> --- title: ऑपरेटर पैटर्न id: operator-pattern date: 2019-05-21 full_link: /docs/concepts/extend-kubernetes/operator/ short_description: > कस्टम संसाधन का प्रबंधन करने के लिए उपयोग किया जाने वाला एक विशेष नियंत्रक aka: tags: - architecture --- [ऑपरेटर पैटर्न](/docs/concepts/extend-kubernetes/operator/) एक सिस्टम रचना है जो {{< glossary_tooltip text="नियंत्रक" term_id="controller" >}} को एक या अधिक कस्टम संसाधनों से जोड़ता है। <!--more--> आप अंतर्निहित नियंत्रक, जो स्वयं कुबेरनेट्स का हिस्सा हैं, का उपयोग करने से परे, अपने क्लस्टर में नियंत्रकों को जोड़कर कुबेरनेट्स की कार्यक्षमता का विस्तार कर सकते हैं। यदि कोई चालू एप्लिकेशन नियंत्रक के रूप में कार्य करता है और उसके पास कंट्रोल प्लेन में परिभाषित कस्टम संसाधन पर कार्य करने के लिए API अभिगम है, तो यह ऑपरेटर पैटर्न का एक उदाहरण है। </ins>

Discussion:
If this is your first contribution, visit for information on how to get started. Review a few to see which content you have to change and which you leave unchanged. Make sure your base, target branch is and create a working branch called . Create a file called content/hi/docs/reference/glossary/operator- Copy the content of to the file you created Localize the content. Push your change and create a pull request. Completing this feature issue fixes part of /language hi /triage accepted
Hello, I want to work on this issue.
/assign
Hey whats the status of your PR?? Are you still working upon it?? if not then do reply me , I will assign this to another folks interested!
/unassign
/assign
Change:
## Enabling sidecar containers <del> Starting with Kubernetes 1.28, a </del> <ins> Enabled by default with Kubernetes 1.29, a </ins> [feature gate](/docs/reference/command-line-tools-reference/feature-gates/) named `SidecarContainers` allows you to specify a `restartPolicy` for containers listed in a Pod's `initContainers` field. These restartable _sidecar_ containers are independent with

Discussion:
This is a Bug Report Problem: text is no longer needed as sidecar containers are now entered into beta state and they are enable by default. reference link of sidecar containers present in page is wrongly redirecting to page. Proposed Solution: the text below from sidecar containers documentation. reference link present in page from page to page. Page to Update:
/sig docs /language en
/assign
Beta APIs are off by default with
is not a beta API though /triage accepted
Change:
| `rolebindings` | | rbac.authorization.k8s.io | true | RoleBinding | | `roles` | | rbac.authorization.k8s.io | true | Role | | `priorityclasses` | `pc` | scheduling.k8s.io | false | PriorityClass | <del> | `storageclasses` | `sc` | storage.k8s.io |  false | StorageClass | </del> <ins> | `csidrivers` | | storage.k8s.io | false | CSIDriver | | `csinodes` | | storage.k8s.io | false | CSINode | | `storageclasses` | `sc` | storage.k8s.io | false | StorageClass | </ins> | `volumeattachments` | | storage.k8s.io | false | VolumeAttachment |

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:
`PreStop` <del> このフックは、APIからの要求、またはliveness probeの失敗、プリエンプション、リソース競合などの管理イベントが原因でコンテナが終了する直前に呼び出されます。コンテナがすでに終了状態または完了状態にある場合、preStopフックの呼び出しは失敗します。 これはブロッキング、つまり同期的であるため、コンテナを停止する信号が送信される前に完了する必要があります。 </del> <ins> このフックは、APIからの要求、またはliveness/startup probeの失敗、プリエンプション、リソース競合などの管理イベントが原因でコンテナが終了する直前に呼び出されます。コンテナがすでに終了状態または完了状態にある場合には`PreStop`フックの呼び出しは失敗し、コンテナを停止するTERMシグナルが送信される前にフックは完了する必要があります。`PreStop`フックが実行される前にPodの終了猶予期間のカウントダウンが開始されるので、ハンドラーの結果に関わらず、コンテナはPodの終了猶予期間内に最終的に終了します。 </ins> ハンドラーにパラメーターは渡されません。 終了動作の詳細な説明は、[Termination of Pods](/ja/docs/concepts/workloads/pods/pod-lifecycle/#pod-termination)にあります。

Discussion:
This is a Feature Request What would you like to be We need to update content/ja/docs/concepts/containers/container-lifecycle- according to the English text, because it is outdated. Why is this needed content/ja/docs/concepts/containers/container-lifecycle- is outdated. Comments /language ja /assign
This issue is currently awaiting triage. SIG Docs takes a lead on issue triage for this website, but any Kubernetes member can accept issues by applying the label. The label can be by org members by writing in a comment. <detailsInstructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details
Change:
sudo port install kubectl ``` <del> 2. Test to ensure the version you installed is up-to-date: </del> <ins> 1. Test to ensure the version you installed is up-to-date: </ins> ```bash kubectl version --client

Discussion:
There are no details or instructions on how to validate the binary downloaded from this page via some form of checksum, sha256 or otherwise. For automation purposes, eg. ansible playbook, being able to validate any binary downloads is a requirement of project stakeholders.
The site doesn't allow browsing, but the file is there as kubectl.sha256 afterall. Might be worth mentioning this in the document?
/retitle Document how to validate kubectl binary against checksum / signature /language en /kind feature /triage accepted The page in question is
To fix this: update to use download links from for example also explain to readers that checksum files are available that they can use to compare binaries obtained from elsewhere for example The and shortcodes are useful for automatically filling in the current Kubernetes version. /help /sig cli
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 : To fix this: update to use download links from explain to readers that checksum files are available that they can use to compare binaries obtained from elsewhere /sig cli 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 may be able to help with this /assign
Change:
--- <del> redirect_from: - "/docs/tutorials/getting-started/create-cluster/" - "/docs/tutorials/getting-started/create-cluster.html" </del> title: 使用 Minikube 创建一个集群 ---

Discussion:
This is a... <!-- choose one by changing [ ] to [x] --- [ ] Feature Request [x] Bug Report Problem: This link: redirects to this page: The link is found here: Proposed Solution: Fix the redirect for /docs/user-guide/working-with-resources Page to Update: Redirect for
Yeah, it's confusing. Why it's P3? How hard to fix it? How I can help?
I know what the problem is and will submit a PR shortly. None of the pages in the /cn directory should have the directive at the top of the page. For example, currently, /cn/docs/tutorials/object-management-kubectl/object- has this set at the top of the page:
Wow! Thank you!!
Ok, nothing should be redirected to the /cn pages anymore. Cheers