jiebi/CodeConvo huggingface dataset:
Change:
the [kubeadm config migrate](/docs/reference/setup-tools/kubeadm/kubeadm-config/) command. For more information on the fields and usage of the configuration you can navigate to our <del> [API reference](/docs/reference/config-api/kubeadm-config.v1beta2/). </del> <ins> [API reference](/docs/reference/config-api/kubeadm-config.v1beta3/). </ins> ## {{% heading "whatsnext" %}}

Discussion:
says: the “configuration format” is a hyperlink to , it shall instead point to (beta2 → beta3) says: where “NodeRegistrationOptions” is a hyperlink to . It shall instead point to (beta2 → beta3) says: where “configuration file” is a hypelink to . It shall instead point to (beta2 → beta3) says: where “API referenc” is a hyperlink to It shall instead point to .
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
/sig cluster-lifecycle /remove-kind bug /kind cleanup
/language en
Change:
Container's working directory. If not specified, the container runtime's default will be used, which might be configured in the container image. Cannot be updated. <del> ### Environment variables {#Environment variables} </del> <ins> ### Environment variables {#Environment-variables} </ins> - **env** ([]EnvVar)

Discussion:
This is a Bug Report The issue is outlined in:
/triage accepted
/kind cleanup
Hi Thanks for opening a PR to fix this issue! /assign
Change:
## static Pod <del> *static Pod*は、{{< glossary_tooltip text="APIサーバー" term_id="kube-apiserver" >}}には管理されない、特定のノード上でkubeletデーモンによって直接管理されるPodのことです。大部分のPodはコントロープレーン(たとえば{{< glossary_tooltip text="Deployment" term_id="deployment" >}})によって管理されますが、static Podの場合はkubeletが各static Podを直接管理します(障害時には再起動します)。 </del> <ins> *static Pod*は、{{< glossary_tooltip text="APIサーバー" term_id="kube-apiserver" >}}には管理されない、特定のノード上でkubeletデーモンによって直接管理されるPodのことです。大部分のPodはコントロールプレーン(たとえば{{< glossary_tooltip text="Deployment" term_id="deployment" >}})によって管理されますが、static Podの場合はkubeletが各static Podを直接管理します(障害時には再起動します)。 </ins> static Podは常に特定のノード上の1つの{{< glossary_tooltip term_id="kubelet" >}}に紐付けられます。static Podの主な用途は、セルフホストのコントロールプレーンを実行すること、言い換えると、kubeletを使用して個別の[コントロールプレーンコンポーネント](/ja/docs/concepts/overview/components/#control-plane-components)を管理することです。

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: There is typo at 177 lines in Proposed Solution: fix "" to "" Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--/language ja /area localization /assign
/triage accepted
Change:
クラウドプロバイダーによっては、`Node Problem Detector`を{{< glossary_tooltip text="Addon" term_id="addons" >}}として有効にしている場合があります。 また、`kubectl`を使って`Node Problem Detector`を有効にするか、`Addon pod`を作成することで有効にできます。 <del> ### kubectlを使用してNodしますroblem Detectorを有効にします {#using-kubectl} </del> <ins> ### kubectlを使用してNode Problem Detectorを有効化します {#using-kubectl} </ins> `kubectl`は`Node Problem Detector`を最も柔軟に管理することができます。 デフォルトの設定を上書きして自分の環境に合わせたり、カスタマイズしたノードの問題を検出したりすることができます。

Discussion:
kubectlNodroblem Detector ↓ kubectlNode Problem Detector <img width="849" alt="Screen Shot 2022-06-23 at 15 43 53" src="https://user-"
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
/language ja /kind bug
/assign
Change:
name: mypod spec: containers: <del> - name: mypod image: redis volumeMounts: - name: foo mountPath: "/etc/foo" readOnly: true volumes: </del> <ins> - name: mypod image: redis volumeMounts: </ins> - name: foo <del> secret: secretName: mysecret optional: true </del> <ins> mountPath: "/etc/foo" readOnly: true volumes: - name: foo secret: secretName: mysecret optional: true </ins> ``` By default, Secrets are required. None of a Pod's containers will start until

Discussion:
Umbrella issue: contains multiple "use cases" for Secrets. However, many of these are mini-tasks. In this issue, I'd like to discuss each of these use cases at a high level to see which we can remove, which we can trim, and which we can move to a new or existing task page. That way, the "Use cases section could even be a bulleted list with links to relevant tasks. Use case: As container environment variables Recommendation: Delete Justification: the goal is achieved in . This also isn't a use case, it's a way to use a secret. Use case: Pod with SSH keys Recommendation: Delete content, keep use case as bullet Justification: the steps add no value beyond the existing task to . Use case: Pods with prod / test credentials Recommendation: Move content to a new or existing task Justification: The content is complex enough that it can be its own task, either as part of or a new task page. Use case: dotfiles in a secret volume Recommendation: Remove steps and keep as bullet point with additional info about why it would be useful. Use case: Secret visible to one container in a Pod Recommendation: Move content to a new or existing task Justification: The content is complex enough that it can be its own task, either as part of or a new task page with actual steps to achieve more than just "secret visible to one container". Perhaps including RBAC steps. If you're interested, review each use case and leave a comment for each agreeing, disagreeing, or providing a different approach to each use case. After we've discussed and settled on an action for these use cases, we can start the actual work! /sig docs /cc
/assign
I think the "Use case: As container environment variables" can be removed as the goal is achieved in too.
Yeah agreed, although I'm separately removing that section and linking it to our existing task page as part of
Let's shift "Use case: Pods with prod/test credentials" and "Use case: secret visible to one container in a Pod" to and attach the link in the use case section as bullet notes.
/triage accepted
Imo the prod/test thing might not even need to move - it can live as an example in the concept but the task steps seem quite basic now that I think about it. Just referencing two Secrets in two different Pods...
Change:
<ins> --- title: FlexVolume id: flexvolume date: 2018-06-25 full_link: /ja/docs/concepts/storage/volumes/#flexvolume short_description: > FlexVolumeは、ツリー外のボリュームプラグインを作成するための非推奨なインターフェースです。{{< glossary_tooltip text="コンテナストレージインターフェース(CSI)" term_id="csi" >}}は、FlexVolumeのいくつかの問題に対処する新しいインターフェースです。 aka: tags: - storage --- FlexVolumeは、ツリー外のボリュームプラグインを作成するための非推奨なインターフェースです。{{< glossary_tooltip text="コンテナストレージインターフェース(CSI)" term_id="csi" >}}は、FlexVolumeのいくつかの問題に対処する新しいインターフェースです。 <!--more--> FlexVolumeを使用すると、ユーザーは独自のドライバーを作成し、Kubernetesでそれらのボリュームをサポートすることができます。 FlexVolumeドライバーのバイナリと依存関係は、ホストマシンにインストールする必要があります。 これにはrootアクセスが必要です。 Storage SIGは、FlexVolumeの制約に対処するために可能であれば{{< glossary_tooltip text="CSI" term_id="csi" >}}ドライバーを実装することを推奨しています。 * [KubernetesドキュメントのFlexVolume](/ja/docs/concepts/storage/volumes/#flexvolume) * [FlexVolumesの詳細な情報](https://github.com/kubernetes/community/blob/master/contributors/devel/sig-storage/flexvolume.md) * [ストレージベンダー向けボリュームプラグインに関するFAQ](https://github.com/kubernetes/community/blob/master/sig-storage/volume-plugin-faq.md) </ins>

Discussion:
Note that this issue is for Japanese Speaker This is a Feature Request What would you like to be Translate into Japanese Why is this needed There is no Japanese translation for this page Comments File to translate: Original: Japanese Localization document: /area localization /language ja /good-first-issue /triage accepted
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 : Note that this issue is for Japanese Speaker Original: /language ja /good-first-issue /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
Change:
<ins> --- title: "示例：配置 java 微服务" weight: 10 --- <!-- --- title: "Example: Configuring a Java Microservice" weight: 10 --- --> </ins>  No newline at end of file

Discussion:
Translate tutorials/configuration/configure-java-microservice/ into Chinese /language zh /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:
<ins> --- title: Kubectlを用いたKubernetesノードのデバッグ content_type: task min-kubernetes-server-version: 1.20 --- <!-- overview --> このページでは、Kubernetesクラスター上で動作している[ノード](/ja/docs/concepts/architecture/nodes/)を`kubectl debug`コマンドを使用してデバッグする方法について説明します。 ## {{% heading "prerequisites" %}} {{< include "task-tutorial-prereqs.md" >}} {{< version-check >}} Podを作成し、それらの新しいPodを任意のノードに割り当てる権限が必要です。 また、ホストのファイルシステムにアクセスするPodを作成する権限も必要です。 <!-- steps --> ## `kubectl debug node`を用いてノードをデバッグする `kubectl debug node`コマンドを使用して、トラブルシューティングしたいノードにPodをデプロイします。 このコマンドは、SSH接続を使用してノードにアクセスできないシナリオで役に立ちます。 Podが作成されると、そのPodはノード上で対話型シェルを開きます。 mynodeという名前のノード上で対話型シェルを作成するには、次のように実行します。 ```shell kubectl debug node/mynode -it --image=ubuntu ``` ```console ノードmynode上に、コンテナデバッガーを持つデバッグ用Pod、node-debugger-mynode-pdx84を作成します。 コマンドプロンプトが表示されない場合は、エンターキーを押してみてください。 root@mynode:/# ``` デバッグコマンドは、情報を収集し、問題をトラブルシューティングするのに役立ちます。 使用する可能性のあるコマンドには、`ip`、`ifconfig`、`nc`、`ping`、`ps`などがあります。 また、`mtr`、`tcpdump`、`curl`などの他のツールもそれぞれのパッケージマネージャーからインストールすることができます。 {{< note >}} デバッグコマンドは、デバッグ用のPodが使用しているイメージに基づいて異なる場合があり、これらのコマンドをインストールする必要があるかもしれません。 {{< /note >}} デバッグ用のPodは、Pod内の`/host`にマウントされたノードのルートファイルシステムにアクセスできます。 kubeletをファイルシステムのネームスペースで実行している場合、デバッグ用のPodはそのネームスペースのルートを見ることになり、ノード全体のルートではありません。 典型的なLinuxノードの場合、関連するログを見つけるために以下のパスを確認できます。 `/host/var/log/kubelet.log` : ノード上でコンテナを実行する責任がある`kubelet`からのログです。 `/host/var/log/kube-proxy.log` : サービスのエンドポイントへのトラフィックを指示する責任がある`kube-proxy`からのログです。 `/host/var/log/containerd.log` : ノード上で実行されている`containerd`プロセスからのログです。 `/host/var/log/syslog` : システムに関する一般的なメッセージや情報です。 `/host/var/log/kern.log` : カーネルログです。 ノード上でデバッグセッションを作成する際には、以下の点を考慮してください。 * `kubectl debug`は、新しいPodの名前をノードの名前に基づいて自動的に生成します。 * ノードのルートファイルシステムは`/host`にマウントされます。 * コンテナはホストのIPC、ネットワーク、PID Namespaceで実行されますが、Podは特権を持っていません。 これは、一部のプロセス情報の読み取りが失敗する可能性があることを意味します。 その情報へのアクセスはスーパーユーザーに制限されているためです。 例えば、`chroot /host`は失敗します。 特権Podが必要な場合は、手動で作成してください。 ## {{% heading "cleanup" %}} デバッグ用のPodの使用が終了したら、それを削除してください。 ```shell kubectl get pods ``` ```none NAME                          READY   STATUS       RESTARTS   AGE node-debugger-mynode-pdx84    0/1     Completed    0          8m1s ``` ```shell # Podの名前は適宜変更してください kubectl delete pod node-debugger-mynode-pdx84 --now ``` ```none pod "node-debugger-mynode-pdx84" deleted ``` {{< note >}} ノードがダウンしている場合(ネットワークから切断されている、kubeletが停止して再起動しないなど)、`kubectl debug node`コマンドは機能しません。 その場合は、[ダウンあるいは到達不能なノードのデバッグ](/ja/docs/tasks/debug/debug-cluster/#example-debugging-a-down-unreachable-node)を確認してください。 {{< /note >}} </ins>

Discussion:
This is a Feature Request What would you like to be Translate into Japanese Why is this needed There is no Japanese translation for this page Comments File to translate: Original: ref. Japanese Localization document: /area localization /language ja /help
/triage accepted
/assign
/remove-help
Change:
There are two types of provisioners for vSphere storage classes: <del> - [CSI provisioner](#csi-provisioner): `csi.vsphere.vmware.com` </del> <ins> - [CSI provisioner](#vsphere-provisioner-csi): `csi.vsphere.vmware.com` </ins> - [vCP provisioner](#vcp-provisioner): `kubernetes.io/vsphere-volume` In-tree provisioners are [deprecated](/blog/2019/12/09/kubernetes-1-17-feature-csi-migration-beta/#why-are-we-migrating-in-tree-plugins-to-csi). For more information on the CSI provisioner, see [Kubernetes vSphere CSI Driver](https://vsphere-csi-driver.sigs.k8s.io/) and [vSphereVolume CSI migration](/docs/concepts/storage/volumes/#csi-migration-5). #### CSI Provisioner {#vsphere-provisioner-csi} <del> The vSphere CSI StorageClass provisioner works with Tanzu Kubernetes clusters. For an example, refer to the [vSphere CSI repository](https://raw.githubusercontent.com/kubernetes-sigs/vsphere-csi-driver/master/example/vanilla-k8s-file-driver/example-sc.yaml). </del> <ins> The vSphere CSI StorageClass provisioner works with Tanzu Kubernetes clusters. For an example, refer to the [vSphere CSI repository](https://github.com/kubernetes-sigs/vsphere-csi-driver/blob/master/example/vanilla-k8s-RWM-filesystem-volumes/example-sc.yaml). </ins> #### vCP Provisioner

Discussion:
links to the wrong Anchor for the CSI Provisioner. It links to #csi-provisioner but should be linking to #vsphere-provisioner-csi Also the link referering to the vsphere CSI repository in delivers a HTTP 404 Status.
/kind bug /language en /triage accepted
/assign
Change:
// Consistent spacing for yaml code .language-yaml > span { height: 1.6em; <del> overflow: hidden; </del> } .content__box

Discussion:
In this section the yaml block is not slidable horizontally which should be.
For me, this issue is reproducible. /area web-development [When the browser window's width is about 2500px] ! [When the browser window's width is about 1240px] !
I had the same issue while working on . I had to get around this by splitting the comments into multiple lines.
/retitle Horizontal scroll not working for code snippet
/kind bug /triage accepted Fixes are welcome
hey! can you assign to me? :D I'll make a PR
/assign
Change:
A selector to restrict the list of returned objects by their fields. Defaults to everything. <hr> --> <del> 根据返回对象的字段限制返回对象列表的选择器。默认为返回所有字段。 </del> <ins> 限制所返回对象的字段的选择器。默认为返回所有字段。 </ins> <hr> ## fieldValidation {#fieldValidation}

Discussion:
should be because fieldSelector is intend to filter objects, not fields. Current translation may lead misunderstanding the functions of fieldSelector
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: /language zh
/assign
/close The understanding is incorrect.
Closing this issue. <detailsIn response to : /close The understanding is incorrect. 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:
## Enabling Resource Quota Resource Quota support is enabled by default for many Kubernetes distributions.  It is <del> enabled when the API server `--enable-admission-plugins=` flag has `ResourceQuota` as </del> <ins> enabled when the {{< glossary_tooltip text="API server" term_id="kube-apiserver" >}} `--enable-admission-plugins=` flag has `ResourceQuota` as </ins> one of its arguments. A resource quota is enforced in a particular namespace when there is a

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. --Change so that the first mention of a “API server” is a for the entry in the glossary. Why is this needed Glossary tooltips help novice users (and people evaluating Kubernetes) to quickly grasp concepts they haven't yet encountered. Comments /language en /triage accepted /priority backlog /kind feature /good-first-issue
This request has been marked as suitable for new contributors. 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 Feature Request <!-- See for guidance on writing an actionable issue description. --<!-- Describe as precisely as possible how this feature/enhancement should work from the user perspective. What should be changed, etc. --Change so that the first mention of a “API server” is a for the entry in the glossary. Glossary tooltips help novice users (and people evaluating Kubernetes) to quickly grasp concepts they haven't yet encountered. Comments /language en /triage accepted /priority backlog /kind feature /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
/assign
Change:
title: Daemon Sets redirect_from: - "/docs/admin/daemons/" <del> - "/docs/admin/daemons/.html" </del> <ins> - "/docs/admin/daemons.html" </ins> --- * TOC

Discussion:
If you visit the browser is trying to download the page because it is served as . I can't understand why. But it's actually trying to do a redirect: Could something be hinting github pages or nginx to interpret this as a non-HTML content? have you seen this in other redirections before?
any ideas?
I think I know what it is. There is a typo in the directive in .
Yup, that did the trick.
Change:
| `priorityclasses` | `pc` | scheduling.k8s.io | false | PriorityClass | | `csidrivers` | | storage.k8s.io | false | CSIDriver | | `csinodes` | | storage.k8s.io | false | CSINode | <del> | `storageclasses` | `sc` | storage.k8s.io |  false | StorageClass | </del> <ins> | `storageclasses` | `sc` | storage.k8s.io | false | StorageClass | </ins> | `volumeattachments` | | storage.k8s.io | false | VolumeAttachment | ## Output options

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:
title: Ingress id: ingress date: 2018-04-12 <del> full_link: /docs/concepts/services-networking/ingress/ </del> <ins> full_link: /pt-br/docs/concepts/services-networking/ingress/ </ins> short_description: > Um objeto da API que gerencia o acesso externo aos serviços em um cluster, normalmente HTTP.

Discussion:
The translated Brazilian Portuguese glossary entry for ingress is slightly out-of-date with its English counterpart. Update the entry so it reflects the latest English version. /language pt /triage accepted /assign
Change:
* {{< include "task-tutorial-prereqs.md" >}} {{< version-check >}} <del> * Install [redis-cli](http://redis.io/topics/rediscli). </del> <ins> * Install [MongoDB Shell](https://www.mongodb.com/try/download/shell). </ins> <!-- steps --> <del> ## Creating Redis deployment and service </del> <ins> ## Creating MongoDB deployment and service </ins> <del> 1. Create a Deployment that runs Redis: </del> <ins> 1. Create a Deployment that runs MongoDB: </ins> ```shell <del> kubectl apply -f https://k8s.io/examples/application/guestbook/redis-master-deployment.yaml </del> <ins> kubectl apply -f https://k8s.io/examples/application/guestbook/mongo-deployment.yaml </ins> ``` The output of a successful command verifies that the deployment was created: ``` <del> deployment.apps/redis-master created </del> <ins> deployment.apps/mongo created </ins> ``` View the pod status to check that it is ready:

Discussion:
uses manifests However, these files were removed in . The new example is using mongodb instead of redis, and so, the document needs to be updated overall. The page to update:
/language en
/kind bug /language en /priority backlog /triage accepted /help Thanks
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 : /kind bug /language en /priority backlog /triage accepted </details
/assign

On Forward a local port to a port on the Pod section this should be
/triage needs-information
Could you please link the page
This page
/triage accepted /kind bug /help
This request has been marked as needing help from a contributor. Please ensure the request meets the requirements listed . If this request no longer meets these requirements, the label can be removed by commenting with the command. <detailsIn response to : /triage accepted /kind bug /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
/remove-triage needs-information
/assign