jiebi/CodeConvo huggingface dataset:
Change:
### 노드에 적용된 cordon 해제 <del> 1.  스케줄 가능(schedulable)으로 표시하여 노드를 다시 온라인 상태로 만든다. </del> <ins> -  스케줄 가능(schedulable)으로 표시하여 노드를 다시 온라인 상태로 만든다. </ins> ```shell # <node-to-drain>을 노드의 이름으로 바꾼다.

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: Broken layout on "kubeadm " ! Proposed Solution: Check and apply upstream changes. Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--/language ko
/assign
/unassign This issue already has been assigned to .
Change:
persistentVolumes, are not in any namespace. --> 大多数 kubernetes 资源（例如 Pod、Service、副本控制器等）都位于某些名字空间中。 <del> 但是名字空间资源本身并不在名字空间中。而且底层资源，例如 [节点](/zh-cn/docs/concepts/architecture/nodes/)和持久化卷不属于任何名字空间。 </del> <ins> 但是名字空间资源本身并不在名字空间中。而且底层资源， 例如[节点](/zh-cn/docs/concepts/architecture/nodes/)和持久化卷不属于任何名字空间。 </ins> <!-- To see which Kubernetes resources are and aren't in a namespace:

Discussion:
markdown <img width="681" alt="WX20220809- src="https://user-"
page: /triage accepted /assign
namespace
Change:
Azure File CSI driver does not support using same volume with different fsgroups, if Azurefile CSI migration is enabled, using same volume with different fsgroups won't be supported at all. <ins> #### azureFile CSI migration complete {{< feature-state for_k8s_version="v1.21" state="alpha" >}} To disable the `azureFile` storage plugin from being loaded by the controller manager and the kubelet, set the `InTreePluginAzureFileUnregister` flag to `true`. </ins> ### cephfs A `cephfs` volume allows an existing CephFS volume to be

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: doesn't mention the feature gate , but it should do. Proposed Solution: Update documentation for migration from in-tree Azure File driver. Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--Additional Information: /sig storage /language en
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:
## References <del> - [Docs for the DNS cluster addon](http://releases.k8s.io/{{page.githubbranch}}/build/kube-dns/README.md) </del> <ins> - [Docs for the DNS cluster addon](http://releases.k8s.io/{{page.githubbranch}}/build-tools/kube-dns/README.md) </ins>

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 reference link at the bottom of the docs page on appears to be broken. the link points to , which redirects to This returns a 404 not found page on github. Proposed Solution: Looking though github, it appears that the kube-dns was moved in github to cluster/addons about 4 months ago under dns. the can be found at now and possibly parts of it were also moved into Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--
Change:
## Daemon Podがどのようにスケジューリングされるか <del> ### デフォルトスケジューラーによってスケジューリングされる場合 </del> <ins> DaemonSetは、全ての利用可能なNodeがPodのコピーを稼働させることを保証します。DaemonSetコントローラーは対象となる各Nodeに対してPodを作成し、ターゲットホストに一致するようにPodの`spec.affinity.nodeAffinity`フィールドを追加します。Podが作成されると、通常はデフォルトのスケジューラーが引き継ぎ、`.spec.nodeName`を設定することでPodをターゲットホストにバインドします。新しいNodeに適合できない場合、デフォルトスケジューラーは新しいPodの[優先度](/ja/docs/concepts/scheduling-eviction/pod-priority-preemption/#pod-priority)に基づいて、既存Podのいくつかを先取り(退避)させることがあります。 </ins> <del> {{< feature-state for_k8s_version="1.17" state="stable" >}} </del> <ins> ユーザーは、DaemonSetの`.spec.template.spec.schedulerName`フィールドを設定することにより、DaemonSetのPodに対して異なるスケジューラーを指定することができます。 </ins> <del> DaemonSetは全ての利用可能なNodeが単一のPodのコピーを稼働させることを保証します。通常、Podが稼働するNodeはKubernetesスケジューラーによって選択されます。しかし、DaemonSetのPodは代わりにDaemonSetコントローラーによって作成され、スケジューリングされます。 下記の問題について説明します: * 矛盾するPodのふるまい: スケジューリングされるのを待っている通常のPodは、作成されているが`Pending`状態となりますが、DaemonSetのPodは`Pending`状態で作成されません。これはユーザーにとって困惑するものです。 * [Podプリエンプション(Pod preemption)](/docs/concepts/configuration/pod-priority-preemption/)はデフォルトスケジューラーによってハンドルされます。もしプリエンプションが有効な場合、そのDaemonSetコントローラーはPodの優先順位とプリエンプションを考慮することなくスケジューリングの判断を行います。 `ScheduleDaemonSetPods`は、DaemonSetのPodに対して`NodeAffinity`項目を追加することにより、DaemonSetコントローラーの代わりにデフォルトスケジューラーを使ってDaemonSetのスケジュールを可能にします。その際に、デフォルトスケジューラーはPodをターゲットのホストにバインドします。もしDaemonSetのNodeAffinityが存在するとき、それは新しいものに置き換えられます(ターゲットホストを選択する前に、元のNodeAffinityが考慮されます)。DaemonSetコントローラーはDaemonSetのPodの作成や修正を行うときのみそれらの操作を実施します。そしてDaemonSetの`.spec.template`フィールドに対しては何も変更が加えられません。 </del> <ins> `.spec.template.spec.affinity.nodeAffinity`フィールド(指定された場合)で指定された元のNodeアフィニティは、DaemonSetコントローラーが対象Nodeを評価する際に考慮されますが、作成されたPod上では対象Nodeの名前と一致するNodeアフィニティに置き換わります。 </ins> ```yaml nodeAffinity:

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
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:
<!-- overview --> <!-- When you deploy Kubernetes, you get a cluster. <del> {{< glossary_definition term_id="cluster" length="all" prepend="A Kubernetes cluster consists of">}} </del> <ins> {{ < glossary_definition term_id="cluster" length="all" prepend="A Kubernetes cluster consists of">}} </ins> This document outlines the various components you need to have for a complete and working Kubernetes cluster. <del> {{< figure src="/images/docs/components-of-kubernetes.svg" alt="Components of Kubernetes" caption="The components of a Kubernetes cluster" class="diagram-large" >}} </del> <ins> {{ < figure src="/images/docs/components-of-kubernetes.svg" alt="Components of Kubernetes" caption="The components of a Kubernetes cluster" class="diagram-large" >}} </ins> --> 当你部署完 Kubernetes，便拥有了一个完整的集群。

Discussion:
!
url Language Chinese
/retitle [zh-cn] Disorganized Layout of 'Kubernetes Components Page' /language zh
/triage accepted /kind bug
/assign
Change:
defines what action the {{< glossary_tooltip text="control plane" term_id="control-plane" >}} takes if a potential violation is detected: --> <del> ## 为名字空间设置 Pod 安全性准入控制标签 </del> <ins> ## 为名字空间设置 Pod 安全性准入控制标签 {#pod-security-admission-labels-for-namespaces} </ins> 一旦特性被启用或者安装了 Webhook，你可以配置名字空间以定义每个名字空间中 Pod 安全性准入控制模式。

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. --add and translate Chinese document: English: Why is this needed Support for more localization. Comments <!-- Any additional related comments that might help. Drawings/mockups would be extremely helpful (if required). --/language zh /assign
/triage accepted
Change:
* `kubectl`：用来与集群通信的命令行工具。 <ins> <!-- kubeadm **will not** install or manage `kubelet` or `kubectl` for you, so you will need to ensure they match the version of the Kubernetes control plane you want kubeadm to install for you. If you do not, there is a risk of a version skew occurring that can lead to unexpected, buggy behaviour. However, _one_ minor version skew between the kubelet and the control plane is supported, but the kubelet version may never exceed the API server version. For example, kubelets running 1.7.0 should be fully compatible with a 1.8.0 API server, but not vice versa. For information about installing `kubectl`, see [Install and set up kubectl](/docs/tasks/tools/). --> </ins> kubeadm **不能** 帮你安装或者管理 `kubelet` 或 `kubectl`，所以你需要 确保它们与通过 kubeadm 安装的控制平面的版本相匹配。 如果不这样做，则存在发生版本偏差的风险，可能会导致一些预料之外的错误和问题。

Discussion:
(kubeadm) []
/triage accepted /kind bug /assign /language zh
Change:
spec: containers: - name: php-redis <del> image: gcr.io/google_samples/gb-frontend:v3 </del> <ins> image: us-docker.pkg.dev/google-samples/containers/gke/gb-frontend:v5 </ins>

Discussion:
Hi Currently we obsrved that following image is not availble
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 en /sig docs
can you please provide the page link of the issue?
HI Kubernetes/Website PFA link
/retitle Container image is not available for /kind bug
This looks similar to issue we already have I think it is a duplicate. /triage duplicate
Thanks for raising this! However, closing this request as it closely mirrors the original issue. Feel free to continue the discussion on the original issue. /close not-planned
Closing this issue, marking it as "Not Planned". <detailsIn response to : Thanks for raising this! 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:
<ins> apiVersion: rbac.authorization.k8s.io/v1 kind: ClusterRole metadata: name: csr-creator rules: - apiGroups: - certificates.k8s.io resources: - certificatesigningrequests verbs: - create - get - list - watch </ins>

Discussion:
/language zh
/reopen This was incorrectly
Reopened this issue. <detailsIn response to : /reopen This was incorrectly Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details
/assign
Change:
PVs of that default. Specifying a default StorageClass is done by setting the annotation `storageclass.kubernetes.io/is-default-class` equal to `true` in a StorageClass object. If the administrator does not specify a default, the <del> cluster responds to PVC creation as if the admission plugin were turned off. If more than one default is specified, the admission plugin forbids the creation of all PVCs. </del> <ins> cluster responds to PVC creation as if the admission plugin were turned off. If more than one default StorageClass is specified, the newest default is used when the PVC is dynamically provisioned. </ins> * If the admission plugin is turned off, there is no notion of a default StorageClass. All PVCs that have `storageClassName` set to `""` can be bound only to PVs that have `storageClassName` also set to `""`.

Discussion:
Here is a statement under the documentation. If more than one default StorageClass is accidentally set, the newest default is used when the PVC is dynamically provisioned. Here is another statement that contradicts with the first one in the documentation. If more than one default is specified, the admission plugin forbids the creation of all PVCs.
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
Pages related to issue: , /language en
/retitle Inconsistencies in default StorageClass behaviour in "Storage Classes" and "Persistent Volumes" pages /sig storage
/sig docs
Change:
| `MemoryPressure`    | `True` if pressure exists on the node memory - that is, if the node memory is low; otherwise `False` | | `PIDPressure`    | `True` if pressure exists on the processes - that is, if there are too many processes on the node; otherwise `False` | | `NetworkUnavailable`    | `True` if the network for the node is not correctly configured, otherwise `False` | <ins> {{< /table >}} </ins> --> {{< table caption = "节点状况及每种状况适用场景的描述" >}} | 节点状况       | 描述        |

Discussion:
The Chinese version of the chapter introducing the concept of misses the explanation of the info field compared to the English version. Please check it.
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
this is fixed here
Change:
Los objetos básicos de Kubernetes incluyen: <del> * [Pod](/docs/concepts/workloads/pods/pod-overview/) </del> <ins> * [Pod](/es/docs/concepts/workloads/pods/pod/) </ins> * [Service](/docs/concepts/services-networking/service/) * [Volume](/docs/concepts/storage/volumes/) <del> * [Namespace](/docs/concepts/overview/working-with-objects/namespaces/) </del> <ins> * [Namespace](/es/docs/concepts/overview/working-with-objects/namespaces/) </ins> Además, Kubernetes contiene abstracciónes de nivel superior llamadas Controladores. Los Controladores se basan en los objetos básicos y proporcionan funcionalidades adicionales sobre ellos. Incluyen: <del> * [ReplicaSet](/docs/concepts/workloads/controllers/replicaset/) * [Deployment](/docs/concepts/workloads/controllers/deployment/) * [StatefulSet](/docs/concepts/workloads/controllers/statefulset/) * [DaemonSet](/docs/concepts/workloads/controllers/daemonset/) * [Job](/docs/concepts/workloads/controllers/jobs-run-to-completion/) </del> <ins> * [ReplicaSet](/es/docs/concepts/workloads/controllers/replicaset/) * [Deployment](/es/docs/concepts/workloads/controllers/deployment/) * [StatefulSet](/es/docs/concepts/workloads/controllers/statefulset/) * [DaemonSet](/es/docs/concepts/workloads/controllers/daemonset/) * [Job](/es/docs/concepts/workloads/controllers/jobs-run-to-completion/) </ins> ## Plano de Control de Kubernetes

Discussion:
This is a Bug Report concepts page for spanish links doesn't take to spanish pages <!--Required Information--Problem: The page is the Spanish translation, the links on this page should take you to the Spanish version of the link when available, if not available then ok to leave it pointing to English Proposed Solution: Update the page links to point to Spanish version (ie. es) Page to Update: I intended to review and submit a PR
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 es
/assign
/assign
Thanks for the report, this is quite common as the translation is a work in progress and we don't have (yet) a way to easily detect where a page is referenced. Let me know if you have any issue working with the PR.
I will work on this page as one-off, and think about how can we automate the detection for all links that should point to the Spanish version.
Maybe something that can be done at build time? Don't know how is the site is build I guess Hugo but not how much pre-processing is done
Change:
## {{% heading "whatsnext" %}} <del> * Learn about the most important basic Kubernetes objects, such as [Pod](/docs/concepts/workloads/pods/). * Learn about [controllers](/docs/concepts/architecture/controller/) in Kubernetes. * [Using the Kubernetes API](/docs/reference/using-api/) explains some more API concepts. </del> <ins> Learn more about the following: * [Pods](https://kubernetes.io/docs/concepts/workloads/pods/) which are the most important basic Kubernetes objects. * [Deployment](https://kubernetes.io/docs/concepts/workloads/controllers/deployment/) objects. * [Controllers](https://kubernetes.io/docs/concepts/architecture/controller/) in Kubernetes. * [Kubernetes API overview](https://kubernetes.io/docs/reference/using-api/) which explains some more API concepts. * [kubectl](https://kubernetes.io/docs/reference/kubectl/) and [kubectl commands](https://kubernetes.io/docs/reference/generated/kubectl/kubectl-commands). </ins>

Discussion:
This is a Bug Report <!--Required Information--Problem: Below information is needed to mention in Kubernetes-objects Learn more about deployments Learn about kubectl and kubectl commands Proposed Solution: Add Below points under Kubernetes-objects Learn more about Learn about and Page to Update:
/language en /assign
/triage accepted Good idea
Fixed it here
Change:
## Creating a local Calico cluster with kubeadm To get a local single-host Calico cluster in fifteen minutes using kubeadm, refer to the <del> [Calico Quickstart](https://docs.projectcalico.org/latest/getting-started/kubernetes/). </del> <ins> [Calico Quickstart](https://projectcalico.docs.tigera.io/getting-started/kubernetes/). </ins>

Discussion:
This is a Bug Report <!-- Thanks for filing an issue! Before submitting, please fill in the following information. --<!-- See for guidance on writing an actionable issue description. --<!--Required Information--Problem: under the 'Use Calico for NetworkPolicy' is leading to an invalid URL resulting in page not found error. Proposed Solution: Updating of Quickstart link in the Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--
/assign
/triage accepted
Hi , great find! Apart from fixing link you can also look for further improvement in overall doc so that one PR can cover more improvements. For eg. fixing Grammatical errors, adding more information in the sections etc.
This seems to be duplicate of /triage duplicate
looks to be reporting broken link on whereas this issue is reporting issue with link on different page
/remove-triage duplicate
Right. my bad. Please consider these points as well:
Change:
#### Load balancers with mixed protocol types <del> {{< feature-state for_k8s_version="v1.24" state="beta" >}} </del> <ins> {{< feature-state for_k8s_version="v1.26" state="stable" >}} </ins> By default, for LoadBalancer type of Services, when there is more than one port defined, all ports must have the same protocol, and the protocol must be one which is supported

Discussion:
This is a Bug Report Problem: The Feature State for is mentioned as under the docs which is wrong. As per mention in the the correct Feature state for is . Proposed Solution: Update the Feature State of MixedProtocolLBService from Kubernetes v1.24 [beta] to Kubernetes v1.26 [stable]. Page to Update:
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 en /sig docs /sig network
I will open a PR for it soon. /assign
Fixed the issue here:
Change:
- title: kube-proxy CLI path: /docs/admin/kube-proxy/ <del> - title: kub-scheduler CLI </del> <ins> - title: kube-scheduler CLI </ins> path: /docs/admin/kube-scheduler/ - title: kubelet CLI

Discussion:
This is a Bug Report This issue appeared recently within kubernetes/website. Links in follow the next pattern , see a square bracket inside of the . I tried to follow in order to find a source of the issue, but wasn't able to do so. my best guesses: Source for generation for 1_17 branch was corrupted. Backend was replaced by something else but not commited (i don't believe in this). This can be temporary content (on ein PR) as toolset for kubernetes-sigs/reference-docs .
/kind bug /priority backlog
ping
I am looking now
, you are referring to a link problem in the reference? I don't immediately see a problem. Can you provide an example of a command that has a link issue? Thanks! I see a link that appears incorrectly formatted, such as the flag in the command, Though, the link does work for me.
I plan on updating the build instructions and README.
any link that follow pattern . If we ware talking about from the root of the kubernetes-sigs/reference-docs, it would be any link in usage block. Almost all of them are anchor links, so problem isn't visible at first. search for or , last symbol of the link is clearly not suppose to be a link (at least its not a link in source yaml) P.S. Is it worth time to update build instructions now? Isn't going to change generator backend to htmlwriter?
, I have a feeling there is a miscommunication. I am not sure what you are referring to. I thought you are logging an issue specifically to the kubectl reference. Please provide a specific example.
ok. for on link to for on link yourself why is in link. diff for kubernetes/website (kubectl-) and see how links are formed. -become right bracket in the href attribute. P.S. just updated one of the search links as i forgot to copy/paste last element of the link (). P.P.S. looks like regular expression issue.
I see. I think we are referring to the same problem -- the right bracket.
Should I close issue or you prefer to have it opened untill kubernetes-sigs/reference-docs is opened?
, I would leave this issue open as a reminder for next release. Thanks! NOTE: The links were manually fixed for the 1.17 release (search/replace).
got it!