jiebi/CodeConvo huggingface dataset:
Change:
Default RBAC policies grant scoped permissions to control-plane components, nodes, and controllers, but grant *no permissions* to service accounts outside the `kube-system` namespace <del> (beyond discovery permissions given to all authenticated users). </del> <ins> (beyond the permissions given by [API discovery roles](#discovery-roles)). </ins> While far more secure, this can be disruptive to existing workloads expecting to automatically receive API permissions. Here are two approaches for managing this transition:

Discussion:
The phrase "beyond discovery permissions given to all authenticated users" in these two sections seems inaccurate. It is quite possible to guess that it references to namely , , , but because of "discovery permissions" phrase it seems to only refer to . It would be better to use different wording, for example: beyond the permissions given by beyond the permissions given by and groups beyond the permissions given by , , cluster roles
/language en /sig docs /kind feature
/retitle Ambiguity in 'beyond discovery permissions' wording in "Using RBAC Authorization" page
/sig auth
/triage accepted A clarification seems reasonable.
/assign
PR working on this issue.
Change:
CSI node plugins need to perform various privileged operations like scanning of disk devices and mounting of file systems. These operations <del> differ for each host operating system. For Linux worker nodes, containerized CSI node node plugins are typically deployed as privileged containers. For Windows worker nodes, </del> <ins> differ for each host operating system. For Linux worker nodes, containerized CSI node plugins are typically deployed as privileged containers. For Windows worker nodes, </ins> privileged operations for containerized CSI node plugins is supported using [csi-proxy](https://github.com/kubernetes-csi/csi-proxy), a community-managed, stand-alone binary that needs to be pre-installed on each Windows node.

Discussion:
Declared "CSIMigration" feature gate only exists in . According to "CSIMigration" could be a switchable feature gate, but it looks like it is always on and cannot be switched off, so it it's strange that it's mentioned in the v1.27 documentation. All of this is probably more or less OK, as it's suitable for earlier versions of Kubernetes especially since there are deprecation warnings. But it’s also unclear for which components this feature gate is intended. According to it's intended for . <brIt is not clear for which components "CSIMigrationAzureFile" feature gate is intended. <brIt is not clear which controller manager is meant — cloud controller manager or kube-controller-manager. According to it's intended for . It is not clear for which components "CSIMigrationRBD" feature gate is intended: <brIt is not clear for which components "SizeMemoryBackedVolumes" feature gate is intended. <brThe description of "nodeExpandSecretRef" field does not start with a new line in the list. <brThe double word "node".
/language en
/assign RakshitKumar04
Let's stop mentioning in You can specify feature gates for all Kubernetes components (some might be no-ops). We could document that, but it'd be better to track that change as a separate issue. Let's remove the double use of node Let's fix the formatting for these are useful things to point out. Thank you! If you find more, you can help further by opening one issue per thing that will need fixing.
/triage accepted
If you prefer to track this as separate issue, whether I should do something extra or not?
If you're willing to file a separate issue about that clarification please do.
I created separate issue , so this issue should be closed after solving everything except point 2.
Hey, should I raise a PR That fixes the following typos here? The description of "nodeExpandSecretRef" field does not start with a new line in the list. The double word "node". For Linux worker nodes, containerized CSI node node plugins are typically deployed as privileged containers.
If it leads to a documentation fix, sure. Sorry, but I don't know enough about the workflow adopted here. I just feel it is my duty to help make the documentation better and I do my best.
Hey, Should I raise a PR correcting the documentation?
Change:
deb http://download.opensuse.org/repositories/devel:/kubic:/libcontainers:/stable:/cri-o:/$VERSION/$OS/ / EOF <del> curl -L https://download.opensuse.org/repositories/devel:/kubic:/libcontainers:/stable/$OS/Release.key | sudo apt-key add --keyring /etc/apt/trusted.gpg.d/libcontainers.gpg curl -L https://download.opensuse.org/repositories/devel:kubic:libcontainers:stable:cri-o:$VERSION/$OS/Release.key | sudo apt-key add --keyring /etc/apt/trusted.gpg.d/libcontainers-cri-o.gpg - </del> <ins> curl -L https://download.opensuse.org/repositories/devel:/kubic:/libcontainers:/stable/$OS/Release.key | sudo apt-key --keyring /etc/apt/trusted.gpg.d/libcontainers.gpg add - curl -L https://download.opensuse.org/repositories/devel:kubic:libcontainers:stable:cri-o:$VERSION/$OS/Release.key | sudo apt-key --keyring /etc/apt/trusted.gpg.d/libcontainers-cri-o.gpg add - </ins> sudo apt-get update sudo apt-get install cri-o cri-o-runc

Discussion:
[UBUNTU 20.04] specifies the following command: This runs into the following error: Update the command to: Or... use the command which is also mentioned on the
Thanks for reporting this. I wonder if we should also recommend that readers ? /kind bug /triage accepted /priority important-longterm /language en /sig node
That is a possibility. But I think it would be logical to take over the official documentation of docker.
Did PR help here? /triage needs-information /remove-triage accepted
/retitle Incorrect commands for adding PGP keys to APT configuration
/triage accepted /remove-triage needs-information
Change:
they could be running CoreDNS Pods or other critical workloads. For more information see [Draining nodes](/docs/tasks/administer-cluster/safely-drain-node/). - All containers are restarted after upgrade, because the container spec hash value is changed. <ins> - To verify that the kubelet service has successfully restarted after the kubelet has been upgraded, you can execute `systemctl status kubelet`  or view the service logs with `journalctl -xeu kubelet`. </ins> <!-- steps -->

Discussion:
For the Redhat when upgrading the kubelet you should have following for Restart kubelet sudo systemctl daemon-reload sudo systemctl stop kubelet ps -ef | grep kubelet (verfiy kubelet stopped kill process if not stopped) sudo systemctl start kubelet
hi, i'm not sure what issue you are reporting. can you elaborate? /kind support
/triage needs-information
/sig cluster-lifecycle I think is asking for a detailed walkthrough of how to restart a service on RedHat-like hosts, and then to verify that the restarted service is healthy. There's some value in this but also we need to bear in mind that systemd and Linux are not the only options for nodes, and that we could instead declare “you should know how to restart services and verify that they are healthy” as a prerequisite. Any Kubernetes-specific way to verify that a kubelet is healthy is valid and we should document it.
Hey can I work on this issue?
we could add the following bullet point here: would you like to send a PR for that?
/kind feature /remove-triage needs-information /triage accepted /retitle kubeadm-upgrade: add note about verifying the kubelet service status
/assign
Change:
the Node is not considered for preemption. {{< /note >}} <del> If a pending Pod has inter-pod affinity to one or more of the lower-priority Pods on the Node, the inter-Pod affinity rule cannot be satisfied in the absence of those lower-priority Pods. In this case, the scheduler does not preempt any Pods on the Node. Instead, it looks for another Node. The scheduler might find a suitable Node or it might not. There is no guarantee that the pending Pod can be scheduled. </del> <ins> If a pending Pod has inter-pod {{< glossary_tooltip text="affinity" term_id="affinity" >}} to one or more of the lower-priority Pods on the Node, the inter-Pod affinity rule cannot be satisfied in the absence of those lower-priority Pods. In this case, the scheduler does not preempt any Pods on the Node. Instead, it looks for another Node. The scheduler might find a suitable Node or it might not. There is no guarantee that the pending Pod can be scheduled. </ins> Our recommended solution for this problem is to create inter-Pod affinity only towards equal or higher priority Pods.

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 should use a glossary tooltip for “affinity” Why is this needed Kubernetes uses the term “affinity” to mean a specific thing. A tooltip (and the hyperlink it implies) helps a reader learn more about this term if they are not sure. Comments /language en
/triage accepted
Hey, I will like to work on this !! Please let me know how can I proceed with this !! !!
/assign
Change:
<ins> --- title: पॉड विघटन (Pod Disruption) id: pod-disruption date: 2021-05-12 full_link: /docs/concepts/workloads/pods/disruptions/ short_description: > पॉड विघटन वह प्रक्रिया है जिसके द्वारा नोड्स पर पॉड्स को स्वेच्छा से या अनैच्छिक रूप से समाप्त कर दिया जाता है। aka: related: - pod - container tags: - operation --- [पॉड विघटन](/docs/concepts/workloads/pods/disruptions/) वह प्रक्रिया है जिसके द्वारा नोड्स पर पॉड्स को स्वेच्छा से या अनैच्छिक रूप से समाप्त कर दिया जाता है। <!--more--> स्वैच्छिक विघटन एप्लीकेशन मालिक या फिर क्लस्टर प्रशासक अभिप्रायपूर्वक चालू करते है। अनैच्छिक विघटन अनजाने में होते है और वो अपरिहार्य वजह से उत्पन्न हो सकते हैं जैसे कि नोड्स के पास संसाधन ख़तम हो जाना या आकस्मिक विलोपन। </ins>

Discussion:
If this is your first contribution, visit for information on how to get started. Review a few to see which content you have to change and which you leave unchanged. Make sure your base, target branch is and create a working branch called . Create a file called content/hi/docs/reference/glossary/pod- Copy the content of to the file you created Localize the content. Push your change and create a pull request. Completing this feature issue fixes part of /language hi /triage accepted
Hi , i can work on this issue. Please assign it to me.
/assign Thank you!
Change:
<h2>Build your cloud native career</h2> <p>Kubernetes is at the core of the cloud native movement. Training and certifications from the Linux Foundation and our training partners lets you invest in your career, learn Kubernetes, and make your cloud native projects successful.</p> </div> <ins> <div class="logo-certification cta-image" id="logo-kcnf"> <img src="/images/training/kubernetes-kcnf-white.svg" /> </div> </ins> <div class="logo-certification cta-image" id="logo-cka"> <img src="/images/training/kubernetes-cka-white.svg"/> </div>

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 Update to mention the qualification. Why is this needed There's now a KCNA qualification that you can train for. Comments /kind feature /language en /priority important-longterm
/help /triage accepted
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 : /help /triage accepted Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details
/assign (I just modified the in the training folder, please LMK if that was not the right way)
That's how we do it. As a separate issue: it'd be nice to convert that to a kind of HTML that's closer to what Docsy renders our site to.
Change:
[build.environment] NODE_VERSION = "10.20.0" <del> HUGO_VERSION = "0.111.3" </del> <ins> HUGO_VERSION = "0.120.3" </ins> [context.production.environment] HUGO_BASEURL = "https://kubernetes.io/"

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 Update Hugo to (or later), by editing Update 2024-01-01: v0.121.1 would be ideal. Why is this needed There are some security fixes for Go that we might want to pull in. Comments /sig security /sig docs
/triage accepted /priority important-longterm
/assign I'd like to help with this
I think just editing the won't work, Would need to update some images or makefile as well?
We use ~magic~ technology so that the one edit is all you need to do.
To test it locally, edit the configuration and then run:
Alright sounds good, I'll do the needful
Change:
Some kubelet garbage collection features are deprecated in favor of eviction: <del> | Existing Flag | New Flag | Rationale | | ------------- | -------- | --------- | | `--image-gc-high-threshold` | `--eviction-hard` or `--eviction-soft` | existing eviction signals can trigger image garbage collection | | `--image-gc-low-threshold` | `--eviction-minimum-reclaim` | eviction reclaims achieve the same behavior | | `--maximum-dead-containers` | - | deprecated once old logs are stored outside of container's context | | `--maximum-dead-containers-per-container` | - | deprecated once old logs are stored outside of container's context | | `--minimum-container-ttl-duration` | - | deprecated once old logs are stored outside of container's context | </del> <ins> | Existing Flag | Rationale | | ------------- | --------- | | `--maximum-dead-containers` | deprecated once old logs are stored outside of container's context | | `--maximum-dead-containers-per-container` | deprecated once old logs are stored outside of container's context | | `--minimum-container-ttl-duration` | deprecated once old logs are stored outside of container's context | </ins> ### Eviction thresholds

Discussion:
We say that the ImageGCHighThresholdPercent/ImageGCLowThresholdPercent config option is deprecated for evictionHard settings but this is not true. ImageGC uses and for Garbage collection so these flags are not We should update our documentation to reflect this.
/language en /sig docs /kind bug
/assign
/sig scheduling
/remove-sig scheduling /sig node Eviction is done in kubelet which is in sig-node's domain.
/triage accepted indeed this needs to be clarified. We unlikely will remove these flags soon. So need to fix up docs
Change:
metadata: name: kube-dns-autoscaler namespace: kube-system <del> labels: addonmanager.kubernetes.io/mode: Reconcile </del> --- kind: ClusterRole apiVersion: rbac.authorization.k8s.io/v1 metadata: name: system:kube-dns-autoscaler <del> labels: addonmanager.kubernetes.io/mode: Reconcile </del> rules: - apiGroups: [""] resources: ["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: mentions an annotation prefix that is deprecated / not actually official. Proposed Solution: Remove all mention of annotations from that page. Page to Update: and specifically Additional Information: This is a follow-up to /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
/retitle Remove labels from ”Autoscale the DNS Service in a Cluster”
/assign
Change:
<del> {{ $feed := getJSON .Site.Params.cveFeedBucket }} {{ if ne $feed.version "https://jsonfeed.org/version/1.1" }} {{ warnf "CVE feed shortcode. KEP-3203: CVE feed does not comply with JSON feed v1.1." }} {{ end }} </del> <ins> {{- $url := .Site.Params.cveFeedBucket }} {{- $feed := "" -}} <!-- Try to fetch remote resource from the specified URL --> {{- with resources.GetRemote $url -}} {{- if .Err -}} <!-- Error message if retrieval fails --> {{- $message := printf "Failed to retrieve CVE data: %s" .Err -}} {{- if eq hugo.Environment "production" -}} {{- errorf $message -}} {{- else -}} {{- warnf $message -}} {{- end -}} {{- else -}} <!-- Process the content if retrieval is successful --> {{- $feed = .Content | transform.Unmarshal -}} {{- if ne $feed.version "https://jsonfeed.org/version/1.1" -}} {{- $warningMessage := "CVE feed shortcode. KEP-3203: CVE feed does not comply with JSON feed v1.1." -}} {{- if eq hugo.Environment "production" -}} {{- errorf $warningMessage -}} {{- else -}} {{- warnf $warningMessage -}} {{- end -}} {{- end -}} {{- end -}} {{- else -}} <!-- Error message if unable to fetch the remote resource --> {{- $message := printf "Unable to fetch CVE data from the specified URL: %q" $url -}} {{- if eq hugo.Environment "production" -}} {{- errorf $message -}} {{- else -}} {{- warnf $message -}} {{- end -}} {{- end -}} <!-- Render table only if CVE feed is available, accommodating for offline builds. --> {{ if ne $feed nil }} </ins> <table class="security-cves"> <caption style="caption-side: top;">{{ T "cve_table" }} {{ printf (T "cve_table_date_format_string") ($feed._kubernetes_io.updated_at | time.Format (T "cve_table_date_format")) }}</caption> <thead>

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 Migrate to instead of Hugo's Why is this needed Upstream Hugo has deprecated , which we use. We should aim to migrate to use ; see Comments We may need to upgrade to a newer Hugo as part of this work, or related to it. /area web-development /lifecycle frozen
/triage accepted /priority backlog
Let me see if I can assist with this. Edit: Proposed fix in /assign
Change:
For example: <del> ```yaml apiVersion: rbac.authorization.k8s.io/v1 kind: ClusterRole metadata: name: csr-creator rules: - apiGroups: - certificates.k8s.io resources: - certificatesigningrequests verbs: - create - get - list - watch ``` </del> <ins> {{< codenew file="access/certificate-signing-request/clusterrole-create.yaml" >}} </ins> To allow approving a CertificateSigningRequest:

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:
{{< feature-state for_k8s_version="v1.21" state="stable" >}} <del> You can configure the kubelet to rotate logs automatically. If you configure rotation, the kubelet is responsible for rotating container logs and managing the </del> <ins> The kubelet is responsible for rotating container logs and managing the </ins> logging directory structure. The kubelet sends this information to the container runtime (using CRI), and the runtime writes the container logs to the given location. You can configure two kubelet [configuration settings](/docs/reference/config-api/kubelet-config.v1beta1/), <del> `containerLogMaxSize` and `containerLogMaxFiles`, </del> <ins> `containerLogMaxSize` (default 10Mi) and `containerLogMaxFiles` (default 5), </ins> using the [kubelet configuration file](/docs/tasks/administer-cluster/kubelet-config-file/). These settings let you configure the maximum size for each log file and the maximum number of files allowed for each container respectively.

Discussion:
On Since the "Log rotation" feature is stable and , we may remove the words "You can configure" and "If you configure rotation". BTW, it would be good to mention the following default values, refer to
/language en /sig docs
/sig node
/assign
/kind bug Any updates?
/remove-kind bug /kind feature
/remove-kind feature /kind docs
The label(s) cannot be applied, because the repository doesn't have them. <detailsIn response to : /remove-kind feature /kind docs 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
I think mentioning the defaults for kubelet configuration would be useful. /triage accepted
/priority backlog
/assign
Change:
{{< glossary_tooltip term_id="kubeadm" text="kubeadm" >}} 도구를 사용하여 쿠버네티스 클러스터를 만들고 관리할 수 있다. 사용자 친화적인 방식으로 최소한의 실행 가능하고 안전한 클러스터를 설정하고 실행하는 데 필요한 작업을 수행한다. <del> [kubeadm 설치](/docs/setup/production-environment/tools/kubeadm/install-kubeadm/) 페이지는 kubeadm 설치하는 방법을 보여준다. </del> <ins> [kubeadm 설치](/ko/docs/setup/production-environment/tools/kubeadm/install-kubeadm/) 페이지는 kubeadm 설치하는 방법을 보여준다. </ins> 설치가 끝나면, [클러스터 생성](/docs/setup/production-environment/tools/kubeadm/create-cluster-kubeadm/)이 가능하다. <del> <a class="btn btn-primary" href="/docs/setup/production-environment/tools/kubeadm/install-kubeadm/" role="button" aria-label="kubeadm 설치 가이드 보기">kubeadm 설치 가이드 보기</a> </del> <ins> <a class="btn btn-primary" href="/ko/docs/setup/production-environment/tools/kubeadm/install-kubeadm/" role="button" aria-label="kubeadm 설치 가이드 보기">kubeadm 설치 가이드 보기</a> </ins>

Discussion:
<!-- 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 , the link href is (English). The of is recently in . Proposed Solution: In , Before: After: Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--/assign
/language ko
/triage accepted
Resolved by
Change:
* Пробуете или начинаете работу с Kubernetes * Локально разрабатываете и тестируете кластер <del> Выбрать [решение для запуска на локальной машине](/docs/setup/pick-right-solution/#local-machine-solutions). </del> <ins> Выбрать [решение для запуска на локальной машине](/docs/setup/learning-environment/). </ins> ## Управляемые решения

Discussion:
По ссылке получаю страницу "404"
/language ru /kind bug
Страница на текущий момент не вся актуальна. Используйте английскую версию.
/triage accepted
Change:
</tr> <tr> <del> <td colspan="2">--cloud-provider-gce-l7lb-src-cidrs cidrs&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Default: 130.211.0.0/22,35.191.0.0/16</td> </tr> <tr> <td></td><td style="line-height: 130%; word-wrap: break-word;"><p>CIDRs opened in GCE firewall for L7 LB traffic proxy &amp; health checks</p></td> </tr> <tr> <td colspan="2">--cloud-provider-gce-lb-src-cidrs cidrs&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Default: 130.211.0.0/22,209.85.152.0/22,209.85.204.0/22,35.191.0.0/16</td> </tr> <tr> <td></td><td style="line-height: 130%; word-wrap: break-word;"><p>CIDRs opened in GCE firewall for L4 LB traffic proxy &amp; health checks</p></td> </tr> <tr> </del> <td colspan="2">--cluster-cidr string</td> </tr> <tr>

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: ! xref: Has references to some CLI arguments that are not valid for . Seem to be side effect of changes went into Proposed Solution: Remove the invalid flags from the documentation in Page to Update:
/language en /triage accepted
/assign
/assign
Thanks for taking care of this :)