jiebi/CodeConvo huggingface dataset:
Change:
This page contains a list of commonly used `kubectl` commands and flags. <ins> {{< note >}} These instructions are for Kubernetes v{{< skew currentVersion >}}. To check the version, use the `kubectl version` command. {{< /note >}} </ins> <!-- body --> ## Kubectl autocomplete

Discussion:
Feedback a confusing point about kubectl command on page: <img width="1107" alt="image" src="https://user-""kubectl events " command seems just available in k8s-v1.26 release version, while below v1.26 not work yet. so a brief tip or comment on the page will be easy to understand. FYI.
Page: /language en /kind suggestion
The label(s) cannot be applied, because the repository doesn't have them. <detailsIn response to : Page: /language en /kind suggestion 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
In my opinion, the cheat sheet is accurate for Kubernetes v1.26. However, if someone needs to refer to older documentation, they can access it by using the version selector option in the navigation bar. To improve clarity, the cheat sheet could integrate details from and provide explicit links within the content body to the other available versions. This approach would be more effective than simply relying on the version selector in the top navigation. Would folks consider this suggestion beneficial?
/retitle Improve clarity of kubectl Cheat Sheet with version information
I'd like to see a shortcode that renders as helper text to steer people to the right documentation, and a link to available versions. See for an example where I'd use this: we could replace that text with an even more helpful shortcode.
We could add a comment that this is accurate for this version of the docs. /priority backlog
I recommend the simple comment approach. We can still use version shortcodes, eg in the comment. /triage accepted
/assign
FYI
Change:
<img src="/images/announcements/kccnc-na-2022-white.svg" style="float: right; height: 80px;" /> <a href="https://events.linuxfoundation.org/kubecon-cloudnativecon-north-america/">KubeCon + CloudNativeCon NA 2022</a> <em>Detroit, Michigan + Virtual</em>. message: | <del> 5 days of incredible opportunites to collaborate, learn + share with the entire community!<br /> </del> <ins> 5 days of incredible opportunities to collaborate, learn + share with the entire community!<br /> </ins> October 24 - 28, 2022.

Discussion:
Problem: The text opportunites is mistyped on the announcement section of . For the problem, check the page . File to Update: /good-first-issue /kind document /assign /language en
The label(s) cannot be applied, because the repository doesn't have them. <detailsIn response to : Problem: The text opportunites is mistyped on the announcement section of . For the problem, check the page . /kind document /assign /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
/remove-good-first-issue Banner changes are actually a bit weird.
/language en
/triage accepted
Change:
automatically assigned the `default` service account of the same namespace.  If you get the raw json or yaml for a pod you have created (e.g. `kubectl get pods/podname -o yaml`), you can see the `spec.serviceAccount` field has been <del> [automatically set](working-with-resources/#resources-are-automatically-modified). </del> <ins> [automatically set](/docs/user-guide/working-with-resources/#resources-are-automatically-modified). </ins> You can access the API using a proxy or with a client library, as described in [Accessing the Cluster](/docs/user-guide/accessing-the-cluster/#accessing-the-api-from-a-pod).

Discussion:
I wish /docs/admin/cluster-components/dns/ page existed It's linked from
Change:
main_menu: true weight: 20 content_type: concept <ins> no_list: true </ins> card: name: setup weight: 20

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. --Update Japanese translation sync to original English version Wed Nov 23 15:06:08 2022 +0530. Why is this needed outdated doc Comments <!-- Any additional related comments that might help. Drawings/mockups would be extremely helpful (if required). --/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
/assign
Change:
### Suggest changes Create or update your chosen localized page based on the English original. See <del> [translating content](#translating-content) for more details. </del> <ins> [localize content](#localize-content) for more details. </ins> If you notice a technical inaccuracy or other problem with the upstream (English) documentation, you should fix the upstream documentation first and

Discussion:
This is a Bug Report Problem: The link available for is broken. The has whose value is which is "broken". Proposed Solution: changes to Page to Update: Additional Information: I am willing to submit the PR.
/kind documentation
/assign
/retitle Broken hyperlink for "Translating content" in "Localizing Kubernetes documentation" page /language en
/triage accepted /priority backlog
Change:
<code><b>echo "NODE_PORT=$NODE_PORT"</b></code></p> <p>Now we can test that the app is exposed outside of the cluster using <code>curl</code>, the IP address of the Node and the externally exposed port:</p> <p><code><b>curl http://"$(minikube ip):$NODE_PORT"</b></code></p> <del> {{< note >}}<p>If Docker is the container runtime, a minikube tunnel is needed. This is because Docker Desktop does not support ports. <br> </del> <ins> {{< note >}}<p>If you're running minikube with Docker Desktop as the container driver, a minikube tunnel is needed. This is because containers inside Docker Desktop are isolated from your host computer.<br> </ins> <p>In a separate terminal window, execute:<br> <del> <code><b>$ minikube service kubernetes-bootcamp --url</b></code></p> </del> <ins> <code><b>minikube service kubernetes-bootcamp --url</b></code></p> </ins> <p>The output looks like this: <pre><b>http://127.0.0.1:51082<br>!  Because you are using a Docker driver on darwin, the terminal needs to be open to run it.</b></pre></p> <p>Then use the given URL to access the app:<br> <del> <code><b>$ curl 127.0.0.1:51082</b></code></p> </del> <ins> <code><b>curl 127.0.0.1:51082</b></code></p> </ins> {{< /note >}} <p>And we get a response from the server. The Service is exposed.</p> </div>

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: had some on to pending Proposed Solution: Update to incorporate the feedback from Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--Additional Information: /language en /priority backlog /help Kubernetes documentation .
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 : This is a Bug Report <!-- See for guidance on writing an actionable issue description. --Problem: had some on to pending Update to incorporate the feedback from <!--Kubernetes Version:--/language en /priority backlog /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
/triage accepted
I want to help with this. /assign
Submitted pull request please review.
Change:
{{< include "task-tutorial-prereqs.md" >}} {{< version-check >}} <ins> The `InPlacePodVerticalScaling` [feature gate](/docs/reference/command-line-tools-reference/feature-gates/) must be enabled for your control plane and for all nodes in your cluster. </ins> ## Container Resize Policies

Discussion:
Not able to find which alpha feature gates for
/kind feature /triage accepted // +featureGate=InPlacePodVerticalScaling // +optional ResizePolicy []ContainerResizePolicy This field is controlled by the feature gate . It looks like we need to add a feature gate description. Does anyone want to help? /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 : /kind feature /triage accepted /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
There is a blog under review. I do concur that some docs are needed for such an important feature.
We should mention within didn't cover this detail.
InPlacePodVerticalScaling in also missing in
Fix coming in
Hi , as I am unable see the changes can I add it to the page?
The feature gate issue has been fixed but the feature description needs some more formal documentation. Please feel free to provide some inputs.
sure so we need to add the featureGate thing? here
It is not limited to the feature gate. It is about the feature. We are supposed to provide some brief introduction to this feature. Currently we have some texts on it, but those texts are provided as a blog (see ). Some of the blogs could have been part of the docs task page ().
thanks for clarifying
Note that this is the same issue as
Change:
<ins> --- title: ファイナライザー id: finalizer date: 2021-07-07 full_link: /ja/docs/concepts/overview/working-with-objects/finalizers/ short_description: > 削除対象としてマークされたオブジェクトを完全に削除する前に、特定の条件が満たされるまでKubernetesを待機させるための名前空間付きのキーです。 aka: tags: - fundamental - operation --- ファイナライザーは、削除対象としてマークされたリソースを完全に削除する前に、特定の条件が満たされるまでKubernetesを待機させるための名前空間付きのキーです。 ファイナライザーは、削除されたオブジェクトが所有していたリソースをクリーンアップするように{{<glossary_tooltip text="コントローラー" term_id="controller">}}に警告します。 <!--more--> Kubernetesにファイナライザーが指定されたオブジェクトを削除するように指示すると、Kubernetes APIはそのオブジェクトに`.metadata.deletionTimestamp`を追加し削除対象としてマークして、ステータスコード`202`(HTTP "Accepted")を返します。 コントロールプレーンやその他のコンポーネントがファイナライザーによって定義されたアクションを実行している間、対象のオブジェクトは終了中の状態のまま残っています。 それらのアクションが完了したら、そのコントローラーは関係しているファイナライザーを対象のオブジェクトから削除します。 `metadata.finalizers`フィールドが空になったら、Kubernetesは削除が完了したと判断しオブジェクトを削除します。 ファイナライザーはリソースの{{<glossary_tooltip text="ガベージコレクション" term_id="garbage-collection">}}を管理するために使うことができます。 例えば、コントローラーが対象のリソースを削除する前に関連するリソースやインフラをクリーンアップするためにファイナライザーを定義することができます。 </ins>

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 Comments <!-- Any additional related comments that might help. Drawings/mockups would be extremely helpful (if required). --/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:
ExecStart= # Replace "systemd" with the cgroup driver of your container runtime. The default value in the kubelet is "cgroupfs". # Replace the value of "--container-runtime-endpoint" for a different container runtime if needed. <del> ExecStart=/usr/bin/kubelet --address=127.0.0.1 --pod-manifest-path=/etc/kubernetes/manifests --cgroup-driver=systemd --container-runtime=remote --container-runtime-endpoint=unix:///var/run/containerd/containerd.sock </del> <ins> ExecStart=/usr/bin/kubelet --address=127.0.0.1 --pod-manifest-path=/etc/kubernetes/manifests --cgroup-driver=systemd --container-runtime-endpoint=unix:///var/run/containerd/containerd.sock </ins> Restart=always EOF

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:
<del> --- title: 新しいコンテンツの貢献の概要 linktitle: 概要 content_type: concept main_menu: true weight: 5 --- <!-- overview --> このセクションでは、新しいコンテンツの貢献を行う前に知っておくべき情報を説明します。 <!-- body --> ## 貢献の基本 - KubernetesのドキュメントはMarkdownで書き、Kubernetesのウェブサイトは[Hugo](https://gohugo.io/)を使ってビルドします。 - ソースは[GitHub](https://github.com/kubernetes/website)にあります。Kubernetesのドキュメントは`/content/en/docs/`にあります。リファレンスドキュメントの一部は、`update-imported-docs/`ディレクトリ内のスクリプトから自動的に生成されます。 - [Page content types](/docs/contribute/style/page-content-types/)にHugoによるドキュメントのコンテンツの見え方を記述しています。 - 標準のHugoのshortcodeに加えて、多数の[カスタムのHugo shortcode](/docs/contribute/style/hugo-shortcodes/)を使用してコンテンツの見え方をコントロールしています。 - ドキュメントのソースは`/content/`内にある複数の言語で利用できます。各言語はそれぞれ[ISO 639-1標準](https://www.loc.gov/standards/iso639-2/php/code_list.php)で定義された2文字のコードの名前のフォルダを持ちます。たとえば、英語のドキュメントのソースは`/content/en/docs/`内に置かれています。 - 複数言語でのドキュメントへの貢献や新しい翻訳の開始に関する情報については、[Kubernetesのドキュメントを翻訳する](/docs/contribute/localization)を参照してください。 ## 始める前に {#before-you-begin} ### CNCF CLAに署名する {#sign-the-cla} すべてのKubernetesのコントリビューターは、[コントリビューターガイド](https://github.com/kubernetes/community/blob/master/contributors/guide/README.md)を読み、[Contributor License Agreement(コントリビューターライセンス契約、CLA)への署名](https://github.com/kubernetes/community/blob/master/CLA.md)を**必ず行わなければなりません**。 CLAへの署名が完了していないコントリビューターからのpull requestは、自動化されたテストで失敗します。名前とメールアドレスは`git config`コマンドで表示されるものに一致し、gitの名前とメールアドレスはCNCF CLAで使われたものに一致しなければなりません。 ### どのGitブランチを使用するかを選ぶ pull requestをオープンするときは、どのブランチをベースにして作業するかをあらかじめ知っておく必要があります。 シナリオ | ブランチ :---------|:------------ 現在のリリースに対する既存または新しい英語のコンテンツ | `master` 機能変更のリリースに対するコンテンツ | 機能変更が含まれるメジャーおよびマイナーバージョンに対応する、`dev-<version>`というパターンのブランチを使います。たとえば、機能変更が`v{{< skew nextMinorVersion >}}`に含まれる場合、ドキュメントの変更は``dev-{{< skew nextMinorVersion >}}``ブランチに追加します。 他の言語内のコンテンツ(翻訳) | 各翻訳対象の言語のルールに従います。詳しい情報は、[翻訳のブランチ戦略](/docs/contribute/localization/#branching-strategy)を読んでください。 それでも選ぶべきブランチがわからないときは、Slack上の`#sig-docs`チャンネルで質問してください。 {{< note >}} すでにpull requestを作成していて、ベースブランチが間違っていたことに気づいた場合は、作成者であるあなただけがベースブランチを変更できます。 {{< /note >}} ### 言語ごとのPR pull requestはPRごとに1つの言語に限定してください。複数の言語に同一の変更を行う必要がある場合は、言語ごとに別々のPRを作成してください。 ## コントリビューターのためのツール `kubernetes/website`リポジトリ内の[doc contributors tools](https://github.com/kubernetes/website/tree/master/content/en/docs/doc-contributor-tools)ディレクトリには、コントリビューターとしての旅を楽にしてくれるツールがあります。 </del>

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. --- Update Japanese translation of Remove (this page is merged into new-content index in English page) Why is this needed outdated page Comments <!-- Any additional related comments that might help. Drawings/mockups would be extremely helpful (if required). --/language ja /assign
/triage accepted
Change:
### TopologyKeys Deprecation The Service field `topologyKeys` is now deprecated; all the component features that used this field were previously alpha, and are now also deprecated. <del> We've replaced `topologyKeys` with a way to implement topology-aware routing, called topology-aware hints.  Topology-aware hints are an alpha feature in Kubernetes 1.21. You can read more details about the replacement feature in [Topology Aware Hints](/docs/concepts/services-networking/service-topology/); the related [KEP](https://github.com/kubernetes/enhancements/blob/master/keps/sig-network/2433-topology-aware-hints/README.md) explains the context for why we switched. </del> <ins> We've replaced `topologyKeys` with a way to implement topology-aware routing, called topology-aware hints.  Topology-aware hints are an alpha feature in Kubernetes 1.21. You can read more details about the replacement feature in [Topology Aware Hints](/docs/concepts/services-networking/topology-aware-hints/); the related [KEP](https://github.com/kubernetes/enhancements/blob/master/keps/sig-network/2433-topology-aware-hints/README.md) explains the context for why we switched. </ins> ## Other Updates

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: Topology-aware traffic routing with topology keys is deprecated since 1.21 Confirm if it's removed and remove the related documentation if feature is removed Proposed Solution: Remove Service Topology page Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--Deprecated since 1.21 <!--Additional Information:--
/kind cleanup /language en
I can look into this. /assign
/sign network /triage accepted /priority important-longterm
Thanks
Change:
app.kubernetes.io/name: wordpress app.kubernetes.io/instance: wordpress-abcxzy app.kubernetes.io/version: "4.9.4" <del> app.kubernetes.io/managed-by: helm </del> <ins> app.kubernetes.io/managed-by: Helm </ins> app.kubernetes.io/component: server app.kubernetes.io/part-of: wordpress ...

Discussion:
There is a suggested annotation of: But Helm actually : Which will insert a value of "Helm", with a first character in uppercase. According to , labels are case-sensitive, except for the prefix. (You can notice this discrepancy if you are using the plug-in, as your chart with a lower-case word will always be replaced with upper-case, so a three-way-merge diff shows this as changing every time. I also imagine you could find this if you tried to use the label as a selector) Therefore I recommend that the suggested annotation in this document be replaced with: Caveat: I have no idea if the case changed between helm v2 and v3, but v2 is defunct now, so should be safe to make this change.
This is just an example of what could go in, but I think it might be a good first issue. If you want to work on this, assign yourself to this issue. Update all instances of to , including in the table. You should be able to complete this in GitHub without needing to work on a local clone. For instructions, read .
/language en
Let me help with this. /assign
/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 : /triage accepted /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