jiebi/CodeConvo huggingface dataset:
Change:
For example: - a localization branch sourced from `main` must be merged into `main`. <del> - a localization branch sourced from `release-{{ skew "prevMinorVersion" }}` must be merged into `release-{{ skew "prevMinorVersion" }}`. </del> <ins> - a localization branch sourced from `release-{{% skew "prevMinorVersion" %}}` must be merged into `release-{{% skew "prevMinorVersion" %}}`. </ins> {{< note >}} If your localization branch was created from `main` branch but it is not merged into `main` before new release branch `{{< release-branch >}}` created, merge it into both `main` and new release branch `{{< release-branch >}}`. To merge your localization branch into new release branch `{{< release-branch >}}`, you need to switch upstream branch of your localization branch to `{{< release-branch >}}`.

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 skew used in the examples in the branching strategy section of the is incorrect and this leads to being rendered instead of something like Proposed Solution: Changing the shortcode to use and instead of and should fix this. Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--Please let us know if any help is needed! /good-first-issue /help
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 skew used in the examples in the branching strategy section of the is incorrect and this leads to being rendered instead of something like <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--Please let us know if any help is needed! /help </details
/assign
/triage accepted
Hi is this what you are asking to do in this pr --! sorry, actually I am new to k8s so not much familiar with its related terminologies!
Your PR is the right fix :) You don't see the change in markdown because this is something hugo does. If you visit the deployed preivew on the PR you'll see your change in action.
Change:
## Setup <del> Ensure the RuntimeClass feature gate is enabled (it is by default). See [Feature Gates](/docs/reference/command-line-tools-reference/feature-gates/) for an explanation of enabling feature gates. The `RuntimeClass` feature gate must be enabled on API server _and_ kubelets. 1. Configure the CRI implementation on nodes (runtime dependent). 2. Create the corresponding RuntimeClass resources. </del> <ins> 1. Configure the CRI implementation on nodes (runtime dependent) 2. Create the corresponding RuntimeClass resources </ins> ### 1. Configure the CRI implementation on nodes

Discussion:
RuntimeClass feature gate is GA in 1.20. According to , a GA feature cannot be disabled and the feature gate is no longer needed. The explanation below can be removed.
triage/accepted
/language en
/triage accepted
/assign
Change:
<!-- 1.  Generate the server certificate using the ca.key, ca.crt and server.csr: --> <del> 1.  基于 ca.key、ca.key 和 server.csr 等三个文件生成服务端证书： </del> <ins> 1.  基于 ca.key、ca.crt 和 server.csr 等三个文件生成服务端证书： </ins> openssl x509 -req -in server.csr -CA ca.crt -CAkey ca.key  -CAcreateserial -out server.crt -days 10000 

Discussion:
There is a translation error here. " " should be changed to " ".
/kind bug /language zh /triage accepted /assign
Change:
1. Create a cluster with no Pod Security Standards applied: ```shell <del> kind create cluster --name psa-wo-cluster-pss --image kindest/node:v1.23.0 </del> <ins> kind create cluster --name psa-wo-cluster-pss --image kindest/node:v1.24.0 </ins> ``` The output is similar to this: ``` Creating cluster "psa-wo-cluster-pss" ... <del> ✓ Ensuring node image (kindest/node:v1.23.0) 🖼 </del> <ins> ✓ Ensuring node image (kindest/node:v1.24.0) 🖼 </ins> ✓ Preparing nodes 📦 ✓ Writing configuration 📜 ✓ Starting control-plane 🕹️

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: Apply Pod Security Standards at the Cluster Level documents Pod Security admission defaults, but for Kubernetes v1.23 rather than any more recent release. Proposed Solution: Either: Edit to automatically render with the version of Kubernetes being documented Update for Kubernetes v1.24 Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--Additional Information: /priority backlog /lifecycle frozen /triage accepted
What would need to change here? The Kubernetes minor version in the commands or also the version in the intro paragraph? (wouldn't that remain 1.23 since that's when the feature went beta?)
The tutorial shows you how to deploy a v1.23.x cluster; it should be v1.24. Maybe if we don't specify any version explicitly, that's good enough (I haven't checked, and I'm not very familiar with ). Making that version always match the latest release is left as an exercise for the reaser.
Hi, I have a question if we automatically render the Kubernetes version being documented for the page, would it be okay to mention something along the lines of : ? Thanks.
You can use this shortcode to show the version: See for an example.
Great, now I can try to work on this issue on the lines of the example. Thanks. /assign
Change:
/docs/setup/minikube/     /docs/tasks/tools/ 302 /docs/setup/learning-environment/     /docs/tasks/tools/  302! <ins> /zh/docs/setup/learning-environment/     /zh/docs/tasks/tools/  302! </ins> /docs/setup/learning-environment/kind/  /docs/tasks/tools/  302 /docs/setup/learning-environment/minikube/  /docs/tasks/tools/ 302 /docs/setup/cri/     /docs/setup/production-environment/container-runtimes/   301

Discussion:
No content in this page. !
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 zh /kind bug BTW the fix for this is to copy the redirect that's configured for the English version of the page.
/assign
Change:
The `hosts` file content would look like this: ```shell <del> kubectl exec hostaliases-pod -- cat /etc/hosts </del> <ins> kubectl logs hostaliases-pod </ins> ``` ```none

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: When the status of the pod is Completed, the command below does not work: kubectl exec hostaliases-pod -- cat /etc/hosts With the error : error: cannot exec into a container in a completed pod; current phase is Succeeded Proposed Solution: Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--v1.18.3 <!--Additional Information:--
i am not certain about this but we can't exec into a pod which is completed.There is a regarding this feature to be implemented .But cant find any updates there.
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:
* 클라이언트는 `node2:nodePort`로 패킷을 보낸다. * `node2`는 소스 IP 주소(SNAT)를 패킷 상에서 자신의 IP 주소로 교체한다. <del> * `noee2`는 대상 IP를 패킷 상에서 파드의 IP로 교체한다. </del> <ins> * `node2`는 대상 IP를 패킷 상에서 파드의 IP로 교체한다. </ins> * 패킷은 node 1로 라우팅 된 다음 엔드포인트로 라우팅 된다. * 파드의 응답은 node2로 다시 라우팅된다. * 파드의 응답은 클라이언트로 다시 전송된다.

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: Mismatch between descriptive node names ! Proposed Solution: Change node name from 'noee2' to 'node2' Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--
/language ko /assign
Change:
### Upgrade the kubelet configuration <del> 1.  Call the following command: </del> <ins> -  Call the following command: </ins> ```shell sudo kubeadm upgrade node

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--indentation issue Proposed Solution: Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--18 <!--Additional Information:--fix the page indentation
/sig cluster-lifecycle docs hi, can you show which section you think is wrong or maybe provide a screenshot?
/sig cluster-lifecycle docs Attached screenshots
i don't see the attachments, possibly because you replied via email. try adding them using the GitHub web UI.
! ! ! !
Page alignment or indentation not proper looks.
ok, i can confirm this. hi, was this broken by this PR, or maybe something on the hugo side changed recently?
The Hugo upgrade was PR
/kind bug /priority important-longterm
I've tried to make a work around for this. It looks like tabs shortcodes with code snippets inside them don't play well with shortcodes (see issue ).
I will take a stab at cleaning this up assuming work isn't currently being done. We might have to adjust the page slightly until capture is removed. /assign
I can share some WIP in case it helps
thanks for taking a look and
oof, sorry I saw this after I opened the PR. That does help! I was scratching my head on some of these bugs. Let me know if you want me to modify my PR to incorporate some of your suggestions or vice versa. I was poking fun of the page on twitter and felt obligated to try to fix it :smile:
Busy at the moment I'm afraid. Feel free to snarf any bits that look useful.
Change:
There are two paths to extending the API with [custom resources](/docs/concepts/api-extension/custom-resources/): <del> 1. [CustomResourceDefinition](/docs/tasks/extend-kubernetes/custom-resource-definitions/) </del> <ins> 1. [CustomResourceDefinition](/docs/tasks/extend-kubernetes/custom-resources/custom-resource-definitions/) </ins> lets you declaratively define how the API server should provide your chosen resource API. 1. You can also [implement your own extension API server](/docs/tasks/extend-kubernetes/setup-extension-api-server/) and use the [aggregator](/docs/tasks/extend-kubernetes/configure-aggregation-layer/)

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 a broken link to "CustomResourceDefinition" in concepts/overview/kubernetes-api/ URL: The linked page receives a 404 error: Proposed Solution: The link should be updated to link to Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--
/language en
/assign
Change:
`diff`        | `kubectl diff -f FILENAME [flags]`| ファイルまたは標準出力と、現在の設定との差分を表示します。 `drain`    | `kubectl drain NODE [options]` | メンテナンスの準備のためにNodeをdrainします。 `edit`        | <code>kubectl edit (-f FILENAME &#124; TYPE NAME &#124; TYPE/NAME) [flags]</code> | デファルトのエディタを使い、サーバー上の1つ以上のリソースリソースの定義を編集し、更新します。 <ins> `events`      | `kubectl events` | イベントを一覧表示します。 </ins> `exec`        | `kubectl exec POD [-c CONTAINER] [-i] [-t] [flags] [-- COMMAND [args...]]` | Pod内のコンテナに対して、コマンドを実行します。 `explain`    | `kubectl explain  [--recursive=false] [flags]` | 様々なリソースのドキュメントを取得します。例えば、Pod、Node、Serviceなどです。 `expose`        | <code>kubectl expose (-f FILENAME &#124; TYPE NAME &#124; TYPE/NAME) [--port=port] [--protocol=TCP&#124;UDP] [--target-port=number-or-name] [--name=name] [--external-ip=external-ip-of-service] [--type=type] [flags]</code> | ReplicationController、Service、Podを、新しいKubernetesサービスとして公開します。

Discussion:
This is a Feature Request What would you like to be Add the describe of in-cluster to kubectl document in Japanese. The target file is Why is this needed There is that describe in English. Comments /language ja /assign
/triage accepted
Change:
### Podオーバーヘッド <del> {{< feature-state for_k8s_version="v1.18" state="beta" >}} </del> <ins> {{< feature-state for_k8s_version="v1.24" state="stable" >}} </ins> Podが稼働する時に関連する _オーバーヘッド_ リソースを指定できます。オーバーヘッドを宣言すると、クラスター(スケジューラーを含む)がPodとリソースに関する決定を行うときにオーバーヘッドを考慮することができます。 <del> Podオーバーヘッドを使うためには、PodOverhead[フィーチャーゲート](/ja/docs/reference/command-line-tools-reference/feature-gates/)を有効にしなければなりません。(デフォルトではonです) </del> PodのオーバーヘッドはRuntimeClass内の`overhead`フィールドによって定義されます。 このフィールドを使用することで、RuntimeClassを使用して稼働するPodのオーバーヘッドを指定することができ、Kubernetes内部で使用されるオーバーヘッドを確保することができます。

Discussion:
This is a Feature Request What would you like to be We need to update content/ja/docs/concepts/containers/runtime- according to the English text, because it is outdated. Why is this needed content/ja/docs/concepts/containers/runtime- is outdated. Comments /language ja /assign
/triage accepted
Change:
title: "Scheduling, Preemption and Eviction" weight: 95 content_type: concept <del> description: > In Kubernetes, scheduling refers to making sure that Pods are matched to Nodes so that the kubelet can run them. Preemption is the process of terminating Pods with lower Priority so that Pods with higher Priority can schedule on Nodes. Eviction is the process of proactively terminating one or more Pods on resource-starved Nodes. </del> no_list: true ---

Discussion:
This is a Bug Report Problem: The description and its proceeding text on the scheduling index page are almost duplicated. Proposed Solution: The following text on the index page needs to be removed: Page to Update: /language en
/assign
I have a specific fix in mind: suppress the display of the page description at the start of the page. That way, we retain the tooltips that we want, and we avoid the duplication.
/language en /priority backlog /triage accepted
Change:
<!--overview--> <!-- <del> This page shows you how to specify the type of [cascading deletion](/docs/concepts/workloads/controllers/garbage-collection/#cascading-deletion) </del> <ins> This page shows you how to specify the type of [cascading deletion](/docs/concepts/architecture/garbage-collection/#cascading-deletion) </ins> to use in your cluster during {{<glossary_tooltip text="garbage collection" term_id="garbage-collection">}}. --> 本页面向你展示如何设置在你的集群执行{{<glossary_tooltip text="垃圾收集" term_id="garbage-collection">}} <del> 时要使用的[级联删除](/zh/docs/concepts/workloads/controllers/garbage-collection/#cascading-deletion) </del> <ins> 时要使用的[级联删除](/zh/docs/concepts/architecture/garbage-collection/#cascading-deletion) </ins> 类型。 ## {{% heading "prerequisites" %}}

Discussion:
There is a bug: ,%E4%BA%86%E8%A7%A3%E5%9E%83%E5%9C%BE%E6%94%B6%E9%9B%86.,-%E5%8F%8D%E9%A6%88 This hyperlink is 404, it should be ""
/assign
/triage accepted
The issue was solved by PR . If there is any problem, please give feedback again. /close
Closing this issue. <detailsIn response to : The issue was solved by PR . If there is any problem, please give feedback again. /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:
<!-- ### cloud-controller-manager <del> {{< glossary_definition term_id="cloud-controller-manager" length="short" >}} </del> The cloud-controller-manager only runs controllers that are specific to your cloud provider. If you are running Kubernetes on your own premises, or in a learning environment inside your own PC, the cluster does not have a cloud controller manager.

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: Original text hast been kept along with translated text Proposed Solution: Delete original English text Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--<img width="863" alt="" src="https://user-"
Looks like the is still working even when being commented out. I have encountered this a hundred times when tidying up the Chinese localization, and this is one of the reasons I don't like this shortcode.
/assign
Change:
<!-- overview --> This page shows how to enable and configure encryption of secret data at rest. ## {{% heading "prerequisites" %}} * {{< include "task-tutorial-prereqs.md" >}} {{< version-check >}} * etcd v3.0 or later is required <!-- steps --> ## Configuration and determining whether encryption at rest is already enabled The `kube-apiserver` process accepts an argument `--encryption-provider-config` <del> that controls how API data is encrypted in etcd. An example configuration is provided below. </del> <ins> that controls how API data is encrypted in etcd. The configuration is provided as an API named [`EncryptionConfiguration`](/docs/reference/config-api/apiserver-encryption.v1/). An example configuration is provided below. </ins> {{< caution >}} <del> **IMPORTANT:** For multi-master configurations (with two or more control plane nodes) the encryption configuration file must be the same! Otherwise, the kube-apiserver can't decrypt data stored inside the key-value store. </del> <ins> **IMPORTANT:** For high-availability configurations (with two or more control plane nodes), the encryption configuration file must be the same! Otherwise, the `kube-apiserver` component cannot decrypt data stored in the etcd. </ins> {{< /caution >}} ## Understanding the encryption at rest configuration.

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 Within add a new generated page that documents the format for an encryption configuration. Update to hyperlink to that new reference Why is this needed Within , there is a configuration format for the API server, EncryptionConfiguration. At the moment that format is not documented in Readers may want to look up what that format covers. Comments /sig api-machinery /sig auth /kind feature /language en
/triage accepted
/assign This file is already generated in the generator. All we need to do is to copy it to the website repo.
Change:
```shell # replace x with the patch version you picked for this upgrade <del> sudo kubeadm upgrade apply v{{< skew latestVersion >}}.x </del> <ins> sudo kubeadm upgrade apply v{{< skew currentVersion >}}.x </ins> ``` Once the command finishes you should see: ``` <del> [upgrade/successful] SUCCESS! Your cluster was upgraded to "v{{< skew latestVersion >}}.x". Enjoy! </del> <ins> [upgrade/successful] SUCCESS! Your cluster was upgraded to "v{{< skew currentVersion >}}.x". Enjoy! </ins> [upgrade/kubelet] Now that your control plane is upgraded, please proceed with upgrading your kubelets if you haven't already done so. ```

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 page https://v1- explains how to upgrade a Kubernetes cluster created with kubeadm from version 1.20.x to version 1.21.x, and from version 1.21.x to 1.21.y. (Should be from version 1.19.x to version 1.20.x, and from version 1.20.x to 1.20.y.) Proposed Solution: In Replace =- =- ... Page to Update: https://v1- <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--/assign
I think we should fix the shortcode to use the documented version, rather than the most recent release. /sig cluster-lifecycle /language en
the intent behind seems to be misleading if is fed at build time pointing at the latest current k8s version. while extending the latestVersion shortcodes i expected to be static and hardcoded per k/website release branch. i can send PRs for this but i'd need to understand more about the "documented" version that you mentioned. i.e. making latestVersion fixed to 1.20 in the 1.20 release branch seems reasonable to me.
^ for additional opinions.
Despite a misleading name, is supposed to use not . AIUI.
i can see is being used in a few places: should all of these be modified to use or only the shortcodes in ? and for which branches - and ?
is useful, it does represent the most recent release.
ok, i can PR the change for 1.20, and master since this is only a problem for the kubeadm upgrade docs. is also used here, but the versions there are just examples. https://v1-
here are the PRs:
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
/remove-lifecycle stale
/triage accepted
/priority-important longterm
The label(s) cannot be applied, because the repository doesn't have them. <detailsIn response to : /priority-important longterm 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
/priority important-longterm