jiebi/CodeConvo huggingface dataset:
Change:
{{ $pageArg := .Get "page" }} {{ $anchorArg := .Get "anchor" }} {{ $textArg := .Get "text" }} <del> {{ $page := site.GetPage "page" (printf "%s/%s" $base $pageArg) }} </del> <ins> {{ $pagePath := path.Join $base $pageArg }} {{ $page := site.GetPage "page" $pagePath }} {{ with $page }}{{else}}{{ range where site.Home.AllTranslations "Language.Lang" "en" }}{{ $page = .Site.GetPage "page" $pagePath }}{{ end }}{{ end }} </ins> {{ $metadata := $page.Params.api_metadata }} <a href="{{ $page.RelPermalink }}{{if $anchorArg}}#{{ $anchorArg }}{{end}}">{{if $textArg}}{{ $textArg }}{{else if $anchorArg}}{{ $anchorArg }}{{else}}{{ $metadata.kind }}{{end}}</a>  No newline at end of file

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: shortcode is not working in localized pages. found this in the PR . en: ja: https://deploy-preview---kubernetes-io-main- ... Proposed Solution: Update so that if the localized version of api reference for current lang exists (e.g. ), then shortcode generates a link that points to the localized version of api reference. if the localized version of api reference for current lang does not exist, then shortcode generates a link that points to the English version of api reference. File to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--
After we resolve this, it might be great to backport this fix.
/triage accepted /area localization
/assign
Per , would you be willing to backport the change to the v1.23 and v1.22 releases?
Please let me know. I know that kubernetes/kubernetes has the following documentation Is there the method for backport in kubernetes/website? Should I create two new PRs for v1.23 and v1.22 with the old release as the merge destination?
Change:
<ins> <script defer src="https://katacoda.com/embed.js"></script> </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 For pages that use Katacoda, add a warning about its removal. Why is this needed Prompted by and Comments /priority critical-urgent /language en /triage accepted
Change:
- All of the above - [Local](#local) <del> {{< feature-state state="stable" for_k8s_version="v1.17" >}} </del> [CSI volumes](/docs/concepts/storage/volumes/#csi) are also supported with dynamic provisioning and pre-created PVs, but you'll need to look at the documentation for a specific CSI driver to see its supported topology keys and examples. {{< note >}} If you choose to use `WaitForFirstConsumer`, do not use `nodeName` in the Pod spec <del> to specify node affinity. If `nodeName` is used in this case, the scheduler will be bypassed and PVC will remain in `pending` state. </del> <ins> to specify node affinity. If `nodeName` is used in this case, the scheduler will be bypassed and PVC will remain in `pending` state. </ins> Instead, you can use node selector for hostname in this case as shown below. {{< /note >}}

Discussion:
There's a section for ReclaimPolicy, which states that this can be or . It is not clear as to what those states mean, there's NO explanation. I was researching how to expand disk, and one guide says that the must be , but I cannot find reference as to what this means. My expectation was that these would be explained what they mean, rather than this is the only do option.
Page related to issue: /retitle Lack of explanation for options - Retain and Delete /language en
These concepts are well explained in 'concepts/storage/persistent-'. Maybe a pointer or two suffices?
Please refer link here you will find the brief introduction about the retain or delete. I think this link will be helpful to understand.
/assign
/triage accepted
Change:
3. allows connections to TCP port 6379 of "role=db" pods in the "default" namespace from any pod in a namespace with the label "project=myproject" 3. allows connections from any pod in the "default" namespace with the label "role=db" to CIDR 10.0.0.0/24 on TCP port 5978 <del> See the [NetworkPolicy getting started guide](/docs/getting-started-guides/network-policy/walkthrough) for further examples. </del> <ins> See the [Declare Network Policy](/docs/tasks/administer-cluster/declare-network-policy/) walkthrough for further examples. </ins> ## Default policies

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 in is broken Proposed Solution: Fix the link Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--
/assign
/assign That patch is a more complete one.
GitHub didn't allow me to assign the following users: kairen. Note that only can be assigned. <detailsIn response to : /assign 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: Kubernetes API 总览 <del> reviewers: - erictune - lavalamp - jbeda </del> content_template: templates/concept weight: 10 card:

Discussion:
This is a Feature Request Since v1.16, extensions/v1beta1 has been deleted and it should not be used in docs What would you like to be The following pages should be edited due to this deletion. [ ] [ ] [x] [ ] [ ] [ ] [ ] [ ] [x] [x] Why is this needed extensions/v1beta1 is deleted in 1.16 Comments
/kind cleanup /priority important-soon (I think)
If you are looking at this as potentially something to contribute to, it's OK to suggest a PR that fixes only one page, or only some pages. If you do that please mention “Partial fix for issue ” in the description of your PR.
thanks for contribution here. Could you please share which pages would you take? Let us make the assignment more clear and help other contributors easily start their work.
Thank you for your comments. I wrote the target file into PR titles. And I will write to the comment about netlify demo pages and original pages to enable checking the diff easily.
Change:
### Linux ```shell <del> export KUBECONFIG_SAVED=$KUBECONFIG </del> <ins> export KUBECONFIG_SAVED="$KUBECONFIG" </ins> ``` ### Windows PowerShell

Discussion:
Setting KUBECONFIG variable doesn't work very well on macOS (Monterey 12.2.1). In the line: The first colon (:) will make the following character (c) dissappear: What I get is the mangled text: What works for me better is explicitly using full paths:
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
The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs. This bot triages issues and PRs according to the following rules: After 90d of inactivity, is applied After 30d of inactivity since was applied, is applied After 30d of inactivity since was applied, the issue is closed You can: Mark this issue or PR as fresh with Mark this issue or PR as rotten with Close this issue or PR with Offer to help out with [Issue Triage][1] Please send feedback to sig-contributor-experience at . /lifecycle stale [1]:
Thanks for reporting, I can open a PR to fix this! /remove-lifecycle stale /assign
Change:
effect: "NoSchedule" ``` <del> ### Handling multiple Windows versions in the same cluster </del> <ins> ### 同じクラスター内の複数Windowsバージョンの管理 </ins> <del> The Windows Server version used by each pod must match that of the node. If you want to use multiple Windows Server versions in the same cluster, then you should set additional node labels and nodeSelectors. </del> <ins> 各Podで使用されるWindows Serverのバージョンは、ノードのバージョンと一致している必要があります。 同じクラスター内で複数のWindows Serverバージョンを使用したい場合は、追加のノードラベルとnodeSelectorsを設定する必要があります。 </ins> <del> Kubernetes 1.17 automatically adds a new label `node.kubernetes.io/windows-build` to simplify this. If you're running an older version, then it's recommended to add this label manually to Windows nodes. </del> <ins> Kubernetes 1.17では、これを簡単するために新しいラベル`node.kubernetes.io/windows-build`が自動的に追加されます。古いバージョンを実行している場合は、このラベルをWindowsノードに手動で追加することをお勧めします。 </ins> <del> This label reflects the Windows major, minor, and build number that need to match for compatibility. Here are values used today for each Windows Server version. </del> <ins> このラベルは、互換性のために一致する必要があるWindowsのメジャー、マイナー、およびビルド番号を反映しています。以下は、Windows Serverの各バージョンで現在使用されている値です。 </ins> <del> | Product Name                         |   Build Number(s)      | </del> <ins> | 製品番号                         　　 |   ビルド番号            | </ins> |--------------------------------------|------------------------| | Windows Server 2019                  | 10.0.17763             | | Windows Server version 1809          | 10.0.17763             | | Windows Server version 1903          | 10.0.18362             | <del> ### Simplifying with RuntimeClass </del> <ins> ### RuntimeClassによる簡素化 </ins> <del> [RuntimeClass] can be used to simplify the process of using taints and tolerations. A cluster administrator can create a `RuntimeClass` object which is used to encapsulate these taints and tolerations. </del> <ins> [RuntimeClass]は、TaintsとTolerationsを使用するプロセスを簡略化するために使用できます。クラスター管理者は、これらのTaintsとTolerationsをカプセル化するために使用する`RuntimeClass`オブジェクトを作成できます。 </ins> <del> 1. Save this file to `runtimeClasses.yml`. It includes the appropriate `nodeSelector` for the Windows OS, architecture, and version. </del> <ins> 1. このファイルを`runtimeClasses.yml`に保存します。これには、Windows OS、アーキテクチャ、およびバージョンに適切な`nodeSelector`が含まれています。 </ins> ```yaml apiVersion: node.k8s.io/v1beta1

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:
* [kubelet configuration (v1beta1)](/docs/reference/config-api/kubelet-config.v1beta1/) * [kube-scheduler configuration (v1beta2)](/docs/reference/config-api/kube-scheduler-config.v1beta2/) * [kube-scheduler configuration (v1beta3)](/docs/reference/config-api/kube-scheduler-config.v1beta3/) <del> * [kube-scheduler policy reference (v1)](/docs/reference/config-api/kube-scheduler-policy-config.v1/) </del> * [kube-proxy configuration (v1alpha1)](/docs/reference/config-api/kube-proxy-config.v1alpha1/) * [`audit.k8s.io/v1` API](/docs/reference/config-api/apiserver-audit.v1/) * [Client authentication API (v1beta1)](/docs/reference/config-api/client-authentication.v1beta1/)

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 scheduler policy API was completely removed in 1.23. Proposed Solution: Revise concepts/configuration/manage-resources- to remove references to the scheduler policy API; Revise or even remove which is meaningless; Remove the kube-scheduler-policy- file from config API. Page to Update: See above. <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--Related:
/sig scheduling /language en
/triage accepted
Change:
コントローラーには以下が含まれます。 * ノードコントローラー：ノードがダウンした場合の通知と対応を担当します。 <del> * レプリケーションコントローラー：システム内の全レプリケーションコントローラーオブジェクトについて、Podの数を正しく保つ役割を持ちます。 * エンドポイントコントローラー：エンドポイントオブジェクトを注入します(つまり、ServiceとPodを紐付けます)。 * サービスアカウントとトークンコントローラー：新規の名前空間に対して、デフォルトアカウントとAPIアクセストークンを作成します。 </del> <ins> * Jobコントローラー：単発タスクを表すJobオブジェクトを監視し、そのタスクを実行して完了させるためのPodを作成します。 * EndpointSliceコントローラー：EndpointSliceオブジェクトを作成します(つまり、ServiceとPodを紐付けます)。 * ServiceAccountコントローラー：新規の名前空間に対して、デフォルトのServiceAccountを作成します。 </ins> ### cloud-controller-manager {{< glossary_definition term_id="cloud-controller-manager" length="short" >}} cloud-controller-managerは、クラウドプロバイダー固有のコントローラーのみを実行します。 <del> KubernetesをオンプレミスあるいはPC内での学習環境で動かす際には、クラスターにcloud container managerはありません。 </del> <ins> Kubernetesをオンプレミスあるいは個人のPC内での学習環境で動かす際には、クラスターにcloud container managerはありません。 kube-controller-managerと同様に、cloud-controller-managerは複数の論理的に独立したコントロールループをシングルバイナリにまとめ、一つのプロセスとして動作します。パフォーマンスを向上させるあるいは障害に耐えるために水平方向にスケールする(一つ以上のコピーを動かす)ことができます。 </ins> <del> kube-controller-managerを使用すると、cloud-controller-managerは複数の論理的に独立したコントロールループをシングルバイナリにまとめ、これが一つのプロセスとして動作します。パフォーマンスを向上させるあるいは障害に耐えるために水平方向にスケールする(一つ以上のコピーを動かす)ことができます。 </del> <ins> 次のコントローラーは、クラウドプロバイダーへの依存関係を持つことがあります。 </ins> <del> 次のコントローラーには、クラウドプロバイダーへの依存関係を持つ可能性があります。 </del> <ins> * Nodeコントローラー：ノードが応答を停止した後、クラウドで削除されたかどうかを判断するため、クラウドプロバイダーをチェックします。 * Routeコントローラー：基盤であるクラウドインフラでルーティングを設定します。 * Serviceコントローラー：クラウドプロバイダーのロードバランサーの作成、更新、削除を行います。 </ins> <del> * ノードコントローラー：ノードが応答を停止した後、クラウドで削除されたかどうかを判断するため、クラウドプロバイダーをチェックします。 * ルーティングコントローラー：基盤であるクラウドインフラでルーティングを設定します。 * サービスコントローラー：クラウドプロバイダーのロードバランサーの作成、更新、削除を行います。 </del> ## ノードコンポーネント {#node-components} ノードコンポーネントはすべてのノードで実行され、稼働中のPodの管理やKubernetesの実行環境を提供します。

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. --Updated Japanese translation for the file. Why is this needed There are several updates in and therefore this page is outdated. 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:
如果没有这个准入控制器，一旦镜像被拉取到节点上，任何用户的 pod 都可以通过已了解到的镜像的名称（假设 pod 被调度到正确的节点上）来使用它，而不需要对镜像进行任何授权检查。 当启用这个准入控制器时，总是在启动容器之前拉取镜像，这意味着需要有效的凭证。 <del> ### AlwaysDeny {#alwaysdeny} {{< feature-state for_k8s_version="v1.13" state="deprecated" >}} </del> <ins> ### AlwaysDeny {#alwaysdeny} {{< feature-state for_k8s_version="v1.13" state="deprecated" >}} </ins> <!-- Rejects all requests. AlwaysDeny is DEPRECATED as no real meaning.

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: Page /zh/docs/reference/access-authn-authz/admission-controllers/ display abnormally, these anchor points should start on a new line. Proposed Solution: fix the anchor point format. abnormal format: normal format: Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--
/assign /language zh
Change:
<!-- overview --> <del> In a Kubernetes cluster, the components on the worker nodes - kubelet and kube-proxy - need to communicate with Kubernetes master components, specifically kube-apiserver. </del> <ins> In a Kubernetes cluster, the components on the worker nodes - kubelet and kube-proxy - need to communicate with Kubernetes control plane components, specifically kube-apiserver. </ins> In order to ensure that communication is kept private, not interfered with, and ensure that each component of the cluster is talking to another trusted component, we strongly recommend using client TLS certificates on nodes.

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: uses the outdated term “master” and “master node”. Proposed Solution: Replace references to the control plane that use the term “master” with the current term: “control plane”. Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--Additional Information: /language en /kind cleanup /wg naming
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
/retitle “Kubelet TLS Bootstrapping” uses outdated wording
I would like to take up this issue
/assign
Change:
* Get hands-on experience [assigning CPU resources to containers and Pods](/docs/tasks/configure-pod-container/assign-cpu-resource/). * Read how the API reference defines a [container](/docs/reference/kubernetes-api/workload-resources/pod-v1/#Container) and its [resource requirements](https://kubernetes.io/docs/reference/kubernetes-api/workload-resources/pod-v1/#resources) <del> * Read about [project quotas](https://xfs.org/docs/xfsdocs-xml-dev/XFS_User_Guide/tmp/en-US/html/xfs-quotas.html) in XFS </del> <ins> * Read about [project quotas](https://xfs.org/index.php/XFS_FAQ#Q:_Quota:_Do_quotas_work_on_XFS.3F) in XFS </ins> * Read more about the [kube-scheduler configuration reference (v1beta3)](/docs/reference/config-api/kube-scheduler-config.v1beta3/)

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 of , the link ' in XFS' is broken. It returns 404 Not Found. Proposed Solution: Page to Update: File to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--
/triage accepted
I think we can link to this : . Thoughts?
/language en sure - would you like to open a pull request?
/assign
Change:
title: "Atualizado: Perguntas frequentes (FAQ) sobre a remoção do Dockershim" date: 2022-02-17 slug: dockershim-faq <del> aliases: [ '/dockershim' ] </del> --- **Esta é uma atualização do artigo original [FAQ sobre a depreciação do Dockershim](/blog/2020/12/02/dockershim-faq/),

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: redirects to Proposed Solution: Remove the alias from the Portuguese blog page. Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--Additional Information: /priority critical-urgent /kind bug /area blog I think a side effect of would be to make this kind of mixup less likely.
/triage accepted
Change:
<pre style="background-color:#fff"><span style="color:#000;font-weight:bold">apiVersion</span>:<span style="color:#bbb"> </span>kubeadm.k8s.io/v1beta4<span style="color:#bbb"> </span><span style="color:#bbb"></span><span style="color:#000;font-weight:bold">kind</span>:<span style="color:#bbb"> </span>ClusterConfiguration<span style="color:#bbb"> </span><span style="color:#bbb"></span><span style="color:#000;font-weight:bold">networking</span>:<span style="color:#bbb"> <del> </span><span style="color:#bbb"> </span><span style="color:#bbb">	</span>...<span style="color:#bbb"> </span><span style="color:#bbb"> </del> <ins> </span><span style="color:#bbb">  </span>...<span style="color:#bbb"> </ins> </span><span style="color:#bbb"></span><span style="color:#000;font-weight:bold">etcd</span>:<span style="color:#bbb"> <del> </span><span style="color:#bbb"> </span><span style="color:#bbb">	</span>...<span style="color:#bbb"> </span><span style="color:#bbb"> </del> <ins> </span><span style="color:#bbb">  </span>...<span style="color:#bbb"> </ins> </span><span style="color:#bbb"></span><span style="color:#000;font-weight:bold">apiServer</span>:<span style="color:#bbb"> <del> </span><span style="color:#bbb"> </span><span style="color:#bbb">	</span><span style="color:#000;font-weight:bold">extraArgs</span>:<span style="color:#bbb"> </span><span style="color:#bbb">	  </span>...<span style="color:#bbb"> </span><span style="color:#bbb">	</span><span style="color:#000;font-weight:bold">extraVolumes</span>:<span style="color:#bbb"> </span><span style="color:#bbb">	  </span>...<span style="color:#bbb"> </span><span style="color:#bbb"> </del> <ins> </span><span style="color:#bbb">  </span><span style="color:#000;font-weight:bold">extraArgs</span>:<span style="color:#bbb"> </span><span style="color:#bbb">    </span>...<span style="color:#bbb"> </span><span style="color:#bbb">  </span><span style="color:#000;font-weight:bold">extraVolumes</span>:<span style="color:#bbb"> </span><span style="color:#bbb">    </span>...<span style="color:#bbb"> </ins> </span><span style="color:#bbb"></span>...<span style="color:#bbb"> </span></pre><p>The ClusterConfiguration type should be used to configure cluster-wide settings, including settings for:</p>

Discussion:
The indentation of the example configuration is messy. !
/kind bug /language en page:
Also Consider to remove the exist in the same page under . Note: This page is automatically generated, you are not allowed to directly change the documentation page.
/retitle Messy indentation on kubeadm config reference page
/priority backlog We'd prioritize other improvements over this one. /triage accepted
/assign This is because the Golang source code contains TAB characters instead of SPACEs as a convention, and those TABs are messing up the YAML snippet. I'll work on this.
PR sent for website. PR sent for the generator.
Change:
쿠버네티스 클러스터가 필요하고, kubectl 커맨드-라인 툴이 클러스터와 <del> 통신할 수 있도록 설정되어 있어야 합니다. </del> <ins> 통신할 수 있도록 설정되어 있어야 한다. </ins> 만약, 아직 클러스터를 가지고 있지 않다면, <del> [Minikube](/docs/setup/learning-environment/minikube/)를 사용해서 만들거나, 다음의 쿠버네티스 플레이그라운드 중 하나를 사용할 수 있습니다: </del> <ins> [Minikube](/ko/docs/setup/learning-environment/minikube/)를 사용해서 생성하거나, 다음의 쿠버네티스 플레이그라운드 중 하나를 사용할 수 있다. </ins> * [Katacoda](https://www.katacoda.com/courses/kubernetes/playground) * [Play with Kubernetes](http://labs.play-with-k8s.com/)

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: '' . . . Proposed Solution: . . - . : - . Minikube : /ko/docs/setup/learning-environment/minikube/ Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--
/language ko /assign