jiebi/CodeConvo huggingface dataset:
Change:
<!-- overview --> ガベージコレクションは、Kubernetesがクラスターリソースをクリーンアップするために使用するさまざまなメカニズムの総称です。これにより、次のようなリソースのクリーンアップが可能になります: <del> * [失敗したPod](/ja/docs/concepts/workloads/pods/pod-lifecycle/#pod-garbage-collection) </del> <ins> * [終了したPod](/ja/docs/concepts/workloads/pods/pod-lifecycle/#pod-garbage-collection) </ins> * [完了したJob](/ja/docs/concepts/workloads/controllers/ttlafterfinished/) * [owner referenceのないオブジェクト](#owners-dependents) * [未使用のコンテナとコンテナイメージ](#containers-images)

Discussion:
This is a Feature Request What would you like to be We need to update content/ja/docs/concepts/architecture/garbage- according to the English text, because it is outdated. Why is this needed content/ja/docs/concepts/architecture/garbage- is outdated. A link text to this page from other pages have already been fixed. The current page is still "" and it should be fixed "". 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:
Generates keys and certificate signing requests (CSRs) for all the certificates required to run the control plane. This command also generates partial kubeconfig files with private key data in the  "users &gt; user &gt; client-key-data" field, and for each kubeconfig file an accompanying ".csr" file is created. <del> This command is designed for use in [Kubeadm External CA Mode](https://kubernetes.io/docs/tasks/administer-cluster/kubeadm/kubeadm-certs/#external-ca-mode). It generates CSRs which you can then submit to your external certificate authority for signing. </del> <ins> This command is designed for use in [Kubeadm External CA Mode](/docs/tasks/administer-cluster/kubeadm/kubeadm-certs/#external-ca-mode). It generates CSRs which you can then submit to your external certificate authority for signing. </ins> The PEM encoded signed certificates should then be saved alongside the key files, using ".crt" as the file extension, or in the case of kubeconfig files, the PEM encoded signed certificate should be base64 encoded and added to the kubeconfig file in the "users &gt; user &gt; client-certificate-data" field.

Discussion:
This is a Bug Report <!-- Thanks for filing an issue! Before submitting, please fill in the following information. --<!-- See for guidance on writing an actionable issue description. --<!--Required Information--Problem: The href of contains unwanted . A slash () is missing in the href of . Proposed Solution: Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--/language en /assign
/triage accepted
Change:
* Verbs: `update`, group: `certificates.k8s.io`, resource: `certificatesigningrequests/status` * Verbs: `sign`, group: `certificates.k8s.io`, resource: `signers`, resourceName: `<signerNameDomain>/<signerNamePath>` or `<signerNameDomain>/*` <del> ```yaml apiVersion: rbac.authorization.k8s.io/v1 kind: ClusterRole metadata: name: csr-signer rules: - apiGroups: - certificates.k8s.io resources: - certificatesigningrequests verbs: - get - list - watch - apiGroups: - certificates.k8s.io resources: - certificatesigningrequests/status verbs: - update - apiGroups: - certificates.k8s.io resources: - signers resourceName: - example.com/my-signer-name # example.com/* can be used to authorize for all signers in the 'example.com' domain verbs: - sign ``` </del> <ins> {{< codenew file="access/certificate-signing-request/clusterrole-sign.yaml" >}} </ins> ## Normal User

Discussion:
/language zh
/reopen This was incorrectly
Reopened this issue. <detailsIn response to : /reopen This was incorrectly 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:
<table> <tr><th>String</th><th>API Object</th></tr> <tr><td>"pods"</td><td>Pod</td></tr> <del> <tr><td>"services</td><td>Service</td></tr> </del> <ins> <tr><td>"services"</td><td>Service</td></tr> </ins> <tr><td>"replicationcontrollers"</td><td>ReplicationController</td></tr> <tr><td>"resourcequotas"</td><td>ResourceQuota</td></tr> <tr><td>"secrets"</td><td>Secret</td></tr>

Discussion:
This is a Bug Report Problem: missing double quote (") after the word services in the last table Proposed Solution: Add the missing double quote (") Page to Update:
Change:
このツールの名前は、`kubectl` です。 <del> `kubectl`コマンドラインツールを使うと、Kubernetesクラスターを制御できます。環境設定のために、`kubectl`は、`$HOME/.kube`ディレクトリにある`config`という名前のファイルを探します。他の[kubeconfig](/ja/docs/concepts/configuration/organize-cluster-access-kubeconfig/)ファイルは、`KUBECONFIG`環境変数を設定するか、[`--kubeconfig`](/docs/concepts/configuration/organize-cluster-access-kubeconfig/)フラグを設定することで指定できます。 </del> <ins> `kubectl`コマンドラインツールを使うと、Kubernetesクラスターを制御できます。環境設定のために、`kubectl`は、`$HOME/.kube`ディレクトリにある`config`という名前のファイルを探します。他の[kubeconfig](/ja/docs/concepts/configuration/organize-cluster-access-kubeconfig/)ファイルは、`KUBECONFIG`環境変数を設定するか、[`--kubeconfig`](/ja/docs/concepts/configuration/organize-cluster-access-kubeconfig/)フラグを設定することで指定できます。 </ins> この概要では、`kubectl`の構文を扱い、コマンド操作を説明し、一般的な例を示します。サポートされているすべてのフラグやサブコマンドを含め、各コマンドの詳細については、[kubectl](/docs/reference/generated/kubectl/kubectl-commands/)リファレンスドキュメントを参照してください。 <del> インストール方法については、[kubectlのインストールおよびセットアップ](/ja/docs/tasks/tools/install-kubectl/)をご覧ください。クイックガイドは、[cheat sheet](/docs/reference/kubectl/cheatsheet/) をご覧ください。`docker`コマンドラインツールに慣れている方は、[`kubectl` for Docker Users](/docs/reference/kubectl/docker-cli-to-kubectl/) でKubernetesの同等のコマンドを説明しています。 </del> <ins> インストール方法については、[kubectlのインストールおよびセットアップ](/ja/docs/tasks/tools/install-kubectl/)をご覧ください。クイックガイドは、[チートシート](/ja/docs/reference/kubectl/cheatsheet/)をご覧ください。`docker`コマンドラインツールに慣れている方は、[`kubectl` for Docker Users](/docs/reference/kubectl/docker-cli-to-kubectl/)でKubernetesの同等のコマンドを説明しています。 </ins> <!-- body -->

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: In the Japanese website, two hyperlinks ( --kubeconfig and cheat sheet ) on the Command line tool (kubectl) page are not getting redirected to the Japanese version of the respective pages. Proposed Solution: The Japanese version of these two pages is already available, so I will simply make these two hyperlinks redirect to the respective Japanese page. Page to Update: https://deploy-preview---kubernetes-io-main- <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--! Comments I want to work on this issue. /assign
/language ja
/triage accepted Thanks for pointing this out You can start solving this issue by assigning yourself. However, it is always recommended to pick those issues of localization that is native to you.
Ok, thank you I'll keep this in my mind from now on .
Change:
{{ define "main" }} <ins> {{ partial "handle-version-switch-404.html" . }} </ins> <div class="container-404"> <h4> Perhaps you were looking for:

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: Current page is lost when switching between documentation versions. Steps to reproduce to some page in the docs, for example the version selector at the top of the page to change to 1.17. that it it sends me to the instead of showing me the . Proposed Solution: Keep the relative path when switching versions Page to Update: All <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--Additional Information: Am I wrong that it used to preserve the page you are on when switching versions? I feel like it used to do that, but I'm not 100% sure.
Yes, at some point the site kept the same page when switching between versions.
/kind bug /priority backlog (I think this is a low-priority-backlog sort of issue; it's a frustration, but we have other places where it makes sense to focus effort first).
/area web-development
Change:
baseurl=https://packages.cloud.google.com/yum/repos/kubernetes-el7-$basearch enabled=1 gpgcheck=1 <del> gpgkey=https://packages.cloud.google.com/yum/doc/yum-key.gpg https://packages.cloud.google.com/yum/doc/rpm-package-key.gpg </del> <ins> gpgkey=https://packages.cloud.google.com/yum/doc/rpm-package-key.gpg </ins> exclude=kubelet kubeadm kubectl EOF

Discussion:
I will submit the PR as well Problem: Steps to reproduce this will result in the following error: Proposed Solution: Remove the 1st key which was used for doing repogpgkey check however since the repogpgcheck option got removed so this 1st key is no longer used/needed. So this would be the fix: Page to Update:
/assign
/triage accepted
Change:
--> Kubernetes 控制面会为所有名字空间设置一个不可变更的 {{< glossary_tooltip text="标签" term_id="label" >}} <del> `kubernetes.io/metadata.name`，只要 `NamespaceDefaultLabelName` 这一 [特性门控](/zh-cn/docs/reference/command-line-tools-reference/feature-gates/) 被启用。标签的值是名字空间的名称。 </del> <ins> `kubernetes.io/metadata.name`，只要 `NamespaceDefaultLabelName` 这一[特性门控](/zh-cn/docs/reference/command-line-tools-reference/feature-gates/)被启用。 标签的值是名字空间的名称。 </ins> ## {{% heading "whatsnext" %}}

Discussion:
markdown <img width="681" alt="WX20220809- src="https://user-"
page: /triage accepted /assign
namespace
Change:
requests: storage: 20Gi --- <del> apiVersion: apps/v1beta2 # for versions before 1.8.0 use apps/v1beta1 </del> <ins> apiVersion: apps/v1 # for versions before 1.9.0 use apps/v1beta2 </ins> kind: Deployment metadata: name: wordpress

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: Deployment yaml file: mysql- api version does not fit 1.9 version: apiVersion: apps/v1beta2 # for versions before 1.8.0 use apps/v1beta1 kind: Deployment Proposed Solution: change apiVersion to: apps/v1 Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--Kubernetes Version: 9 ! <!--Additional Information:--
Change:
A kubelet restart will be required after changing `/var/lib/kubelet/config.conf` or `/var/lib/kubelet/kubeadm-flags.env`. <del> {{% heading "whatsnext" %}} </del> <ins> ## {{% heading "whatsnext" %}} </ins> - [Upgrading kubeadm clusters](/docs/tasks/administer-cluster/kubeadm/kubeadm-upgrade) - [Customizing components with the kubeadm API](/docs/setup/production-environment/tools/kubeadm/control-plane-flags) - [Certificate management with kubeadm](/docs/tasks/administer-cluster/kubeadm/kubeadm-certs) <ins> - [Find more about kubeadm set-up](/docs/reference/setup-tools/kubeadm/) </ins>

Discussion:
This is a Bug Report <!-- Thanks for filing an issue! Before submitting, please fill in the following information. --<!-- See for guidance on writing an actionable issue description. --<!--Required Information--Problem: The document kubeadm- had a format error for section. you can find it More information regarding kubeadm can be . Proposed Solution: section should be in the right format like other documents for eg: Page to Update: /kind bug /language en /assign
/triage accepted /kind bug
Change:
{{ else }} <div class="quote banner"> {{ end }} <del> <p class="quote-text"> {{ .Inner }} </del> <ins> <div class="quote-text"> {{ .Inner | markdownify }} </ins> {{ if .Get "author" }} <span class="quote-author">&mdash; {{ .Get "author" }}</span> {{ end }} <del> </p> </del> <ins> </div> </ins> </div>

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:
/docs/admin/kube-scheduler/     /docs/reference/generated/kube-scheduler/ 301 /docs/admin/kube-scheduler/     /docs/reference/generated/kube-scheduler/ 301 /docs/admin/kubeadm/     /docs/reference/generated/kubeadm/ 301 <ins> /docs/admin/kubelet/      /docs/reference/generated/kubelet/ 301 </ins> /docs/admin/federation-controller-manager/    /docs/reference/generated/federation-controller-manager/ 301 /docs/admin/federation-apiserver/      /docs/reference/generated/federation-apiserver/ 301 /docs/admin/kubefed/     /docs/reference/generated/kubefed/ 301

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: The link of kubelet is broken. The directed page gives 404. doesn't redirect to Proposed Solution: It should redirect to Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--
I will have a look about it
Change:
* Translate a Docker Compose file into Kubernetes objects * Go from local Docker development to managing your application via Kubernetes * Convert v1 or v2 Docker Compose `yaml` files or [Distributed Application Bundles](https://docs.docker.com/compose/bundles/) <ins> ## Kui [`Kui`](https://github.com/kubernetes-sigs/kui) is a GUI tool that takes your normal `kubectl` command line requests and responds with graphics. Kui takes the normal `kubectl` command line requests and responds with graphics. Instead of ASCII tables, Kui provides a GUI rendering with tables that you can sort. Kui lets you: * Directly click on long, auto-generated resource names instead of copying and pasting * Type in `kubectl` commands and see them execute, even sometimes faster than `kubectl` itself * Query a {{< glossary_tooltip text="Job" term_id="job">}} and see its execution rendered as a waterfall diagram * Click through resources in your cluster using a tabbed UI </ins>  No newline at end of file

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 Mention kui within Why is this needed We should make the tool more prominent. Comments Based on an idea from /kind feature /triage accepted /language en /priority backlog
I would make this change by editing and adding a new entry that describes kui. /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 : I would make this change by editing and adding a new entry that describes kui. /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
/sig cli
Hi , I would like to work on this issue. /assign
I have one question: While describing about about kui, should I also include some of its uses?
Change:
```yaml apiVersion: kubeadm.k8s.io/v1beta3 kind: JoinConfiguration <del> nodeRegistration: patches: directory: /home/user/somedir </del> <ins> patches: directory: /home/user/somedir </ins> ``` The directory must contain files named `target[suffix][+patchtype].extension`.

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 yaml for control-plane-flags patch section has an incorrect structure. Please see the InitConfiguration definition here: Proposed Solution: It should be like this: Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--23 <!--Additional Information:--
I'd prepare a PR on this, but cloning the repo takes forever. Will do that tomorrow.
That is indeed a bug in the docs. Thanks for logging the ticket. /assign /sig cluster-lifecycle
i can send the PR, but if you'd like to contribute in the future you must also sign the CLA.
Sure thing. Will do! Thanks for the heads up!
PR is up /triage accepted
Change:
app: win-webserver spec: ports: <del> # the port that this service should serve on </del> <ins> # このサービスが提供するポート </ins> - port: 80 targetPort: 80 selector:

Discussion:
This is a Feature Request What would you like to be Translate docs/setup/production-environment/windows/user-guide-windows-containers/ into Japanese Why is this needed This page has not been translated. Comments /language ja /assign
Change:
[input_placeholder_email_address] other = "adresse email" <ins> [latest_release] other = "Dernière version:" [end_of_life] other = "Fin du support:" [previous_patches] other = "Correctifs publiés:" [release_date_before] other = "(publiée: " </ins>

Discussion:
This is a Bug Report <!-- Thanks for filing an issue! Before submitting, please fill in the following information. --<!-- See for guidance on writing an actionable issue description. --<!--Required Information--Problem: is blank for the main page content. Proposed Solution: Delete (fall back to English) Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--Additional Information: /language fr
/triage accepted
It have to be deleted and what do you mean by fall back to english? Could you please elaborate?
I guess falling back means the menu link of the French website should lead to (i.e. its English version) instead of since there is no content in the French version. However, I don't understand where this URL () originates from. The partial seems to be incorrect as it always links to the page (despite the website's language currently in use), doesn't it? E.g., there is the content for the locale, but the navigation menu on still leads to the page, not .
/assign
There are 2 issues here: I took a look and indeed, introduced the issue since it a new page under the subfolder. Moreover, is correct, you can get to these translation by going on the page and clicking the language dropdown, and selecting Français but the always redirect to the English version.
/area localization
Both issues were resolved and merged!
Change:
Here's a configuration file for a Deployment. The file does not specify `strategy` or `selector`: <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> ``` Print the live configuration using `kubectl get`: ```shell <del> kubectl get -f http://k8s.io/docs/concepts/tools/kubectl/simple_deployment.yaml -o yaml </del> <ins> kubectl get -f http://k8s.io/docs/tutorials/object-management-kubectl/simple_deployment.yaml -o yaml </ins> ``` The output shows that the API server set several fields to default values in the live

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: