jiebi/CodeConvo huggingface dataset:
Change:
Once a request passes all admission controllers, it is validated using the validation routines for the corresponding API object, and then written to the object store (shown as step **4**). <ins> ## Auditing Kubernetes auditing provides a security-relevant, chronological set of records documenting the sequence of actions in a cluster. The cluster audits the activities generated by users, by applications that use the Kubernetes API, and by the control plane itself. For more information, see [Auditing](/docs/tasks/debug-application-cluster/audit/). </ins> ## API server ports and IPs

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 (briefly) mention that access control mechanisms are followed, optionally, by an audit mechanism recording that decision. Why is this needed Once the concept of auditing is into the Concepts section, we can update other mentions of that concept to hyperlink there. Comments Also relevant to The task page at already gives some background to the mechanism. It's OK to borrow text from that task page if it makes sense to do so. /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:
<hr> <del> - **fieldPath** (string), 必需的 </del> <ins> - **fieldPath** (string)，必需的 </ins> 在指定 API 版本中要选择的字段的路径。

Discussion:
Hello, I noticed some punctuation errors on page /language zh
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
/retitle Punctuation errors on /remove-kind feature /kind bug
Change:
<ins> --- title: "クラスター" weight: 60 --- </ins>

Discussion:
This is a Feature Request What would you like to be Translate into Japanese. Why is this needed This page has not been translated. Comments /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:
2. To see the rollout status, run: ```shell <del> kubectl rollout status deployment.v1.apps/nginx-deployment </del> <ins> kubectl rollout status deployment/nginx-deployment </ins> ``` The output is similar to this:

Discussion:
I am following the minikube tutorial () and find two different ways to getting the roll-out status of an deployment: vs. I am using locally: What is the difference between these two? Might be a good idea to add a node to step number 3 which explains this.
I think that an appropriate improvement that's in line with your comment is to change to run instead. That sounds reasonable to do. /language en /kind cleanup /triage accepted /help
This request has been marked as needing help from a contributor. Please ensure the request meets the requirements listed . If this request no longer meets these requirements, the label can be removed by commenting with the command. <detailsIn response to : I think that an appropriate improvement that's in line with your comment is to change to run instead. /language en /kind cleanup /triage accepted /help Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details
/retitle Multiple way to refer to Deployment resource confusing in Deployment concept page
/assign
Change:
<del> apiVersion: apps/v1beta2 # for versions before 1.8.0 use apps/v1beta1 </del> <ins> apiVersion: apps/v1 # for versions before 1.9.0 use apps/v1beta2 </ins> kind: Deployment metadata: name: patch-demo

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: Deployment yaml file: mysql- api version does not fit 1.9 version: apiVersion: apps/v1beta2 # for versions before 1.8.0 use apps/v1beta1 kind: Deployment Proposed Solution: change apiVersion to: apps/v1 Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--Kubernetes Version: 9 ! <!--Additional Information:--
Change:
<del> # i18n strings for the Portuguese (main) site. </del> <ins> # i18n strings for the Portuguese (main) site. [caution] other = "Cuidado:" </ins> <del> [deprecation_warning] other = " a documentação não é mais mantida ativamente. A versão que você está visualizando no momento é uma captura instantânea estática. Para obter documentação atualizada, consulte " </del> <ins> [cleanup_heading] other = "Limpando" [community_events_calendar] other = "Calendário de Eventos" [community_forum_name] other = "Fórum" [community_github_name] other = "GitHub" # Community links [community_slack_name] other = "Slack" [community_stack_overflow_name] other = "Stack Overflow" [community_twitter_name] other = "Twitter" </ins> [deprecation_file_warning] other = "Descontinuado" <del> [objectives_heading] other = "Objetivos" </del> <ins> [deprecation_warning] other = " a documentação não é mais mantida ativamente. A versão que você está visualizando no momento é uma captura instantânea estática. Para obter documentação atualizada, consulte " </ins> <del> [cleanup_heading] other = "Limpando" </del> <ins> [docs_label_browse] other = "Procurar documentos" </ins> <del> [prerequisites_heading] other = "Antes de você começar" </del> <ins> [docs_label_contributors] other = "Colaboradores" </ins> <del> [whatsnext_heading] other = "Qual é o próximo" </del> <ins> [docs_label_i_am] other = "Eu sou..." [docs_label_users] other = "Usuários" </ins> [feedback_heading] other = "Comentários" <ins> [feedback_no] other = "Não" </ins> [feedback_question] other = "Esta página foi útil?"

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: After PR was merged, the website does not build. This is because the Portuguese localization includes a duplicate translation for a string. Proposed Solution: Remove the duplication Additional Information: /priority critical-urgent /kind bug
Change:
unless the Pod's grace period expires. For more details, see [Termination of Pods](/docs/user-guide/pods/#termination-of-pods). <ins> **Note**: Kubernetes only sends the preStop event when a Pod is *terminated*. This means that the preStop hook is not invoked when the Pod is *completed*. This limitation is tracked in [issue #55087](https://github.com/kubernetes/kubernetes/issues/55807). {: .note} </ins> {% endcapture %}

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 [* ] Bug Report Problem: preStop handler not working when job was deleted Proposed Solution: if issue actually exists along with tests, special statement should be given for documentation Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--9 <!--Additional Information:--
please track this issue: kubernetes/kubernetes At the same time, we should document it.
ok thanks! very expected to proceed it.
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> This allows you to grant particular roles to particular ServiceAccounts as needed. Fine-grained role bindings provide greater security, but require more effort to administrate.

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:
``` kubeadm을 사용하는 경우, <del> [kubelet용 cgroup 드라이버](/docs/setup/production-environment/tools/kubeadm/install-kubeadm/#configure-cgroup-driver-used-by-kubelet-on-control-plane-node)를 수동으로 구성한다. </del> <ins> [kubelet용 cgroup 드라이버](/ko/docs/setup/production-environment/tools/kubeadm/install-kubeadm/#컨트롤-플레인-노드에서-kubelet이-사용하는-cgroup-드라이버-구성)를 수동으로 구성한다. </ins> ### CRI-O

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:
- Use `uniq` to aggregate image counts ```shell <del> kubectl get pods --all-namespaces -o jsonpath="{..image}" | </del> <ins> kubectl get pods --all-namespaces -o jsonpath="{.items[*].spec.containers[*].image}" | </ins> tr -s '[[:space:]]' 'n' | sort | uniq -c

Discussion:
Hi, I've tested this example : It returns image names double, because "{..image}" recursively search in the output of JSON, So at the first, it will find the "image" word in "" and at the second time, it will find the "image" word in "". It means you will see the image name two times for each pod at least. Please change your example. Best Regards, Alireza Bahmani.
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
Hi What's the URL of the page where you've seen a problem?
here are the links to the: kubernetes docs website page ~ markdown file(s) where it require changes ~
The issue is, the following command produces 2 times (the count of image in a single pod). As mentioned, it is because the command count both the occurrence from the & sections from a single pod json manifest. Ideally it should be:
Following could be one of the fix for it:
/assign
There are other references . These would return duplicate images as well, right? I've updated those as well for now.
Hi yes, I feel those also need to be fixed. Let's wait for to provide their review. :)
Change:
| `HugePageStorageMediumSize` | `false` | Alpha | 1.18 | | | `HyperVContainer` | `false` | Alpha | 1.10 | | | `ImmutableEphemeralVolumes` | `false` | Alpha | 1.18 | | <ins> | `IPv6DualStack` | `false` | Alpha | 1.16 | | </ins> | `KubeletPodResources` | `false` | Alpha | 1.13 | 1.14 | | `KubeletPodResources` | `true` | Beta | 1.15 | | | `LegacyNodeRoleBehavior` | `true` | Alpha | 1.16 | |

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--The FeatureGate "IPv6DualStack" does not exist in the feature gate reference page. There is no way to clearly track the support for dual stack as Alpha/Beta/GA.. Proposed Solution: Please add the feature gate referenced in "" in the feature gate reference page Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--version v1.18 <!--Additional Information:--
/assign /kind bug
/sig network
Change:
[Kubernetes 历史上最大的迁移](/zh-cn/blog/2024/05/20/completing-cloud-provider-migration/)中，大约删除了 150 万行代码，将核心组件的二进制文件大小减小了约 40%。在项目早期，很明显可扩展性是成功的关键。 然而，如何实现这种可扩展性并不总是很清楚。此次迁移从核心 Kubernetes 代码库中删除了各种特定于供应商的功能。 <del> 现在，特定于供应商的功能可以通过其他可插拔的扩展功能或模式更好地提供，例如[自定义资源定义（CRD）](https://https://kubernetes.io/zh-cn/docs/concepts/extend-kubernetes/api-extension/custom-resources/) </del> <ins> 现在，特定于供应商的功能可以通过其他可插拔的扩展功能或模式更好地提供，例如[自定义资源定义（CRD）](/docs/concepts/extend-kubernetes/api-extension/custom-resources/) </ins> 或 [Gateway API](https://gateway-api.sigs.k8s.io/) 等 API 标准。 Kubernetes 在为其庞大的用户群体提供服务时也面临着新的挑战，社区正在相应地进行调整。其中一个例子是将镜像托管迁移到新的、由社区拥有的 registry.k8s.io。为用户提供预编译二进制镜像的出口带宽和成本已经变得非常巨大。这一新的仓库变更使社区能够以更具成本效益和性能高效的方式继续提供这些便利的镜像。

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 zh translation of the blog post "10 Years of Kubernetes" has a link which repeats the part of it and thus directs to an inaccessible page. Proposed Solution: Just removing the repetition. Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--This issue is similar to
/assign
/priority backlog /triage accepted
Change:
### Install using native package management {{< tabs name="kubectl_install" >}} <del> {{< tab name="Ubuntu, Debian or HypriotOS" codelang="bash" >}} sudo apt-get update && sudo apt-get install -y apt-transport-https gnupg2 curl curl -s https://packages.cloud.google.com/apt/doc/apt-key.gpg | sudo apt-key add - echo "deb https://apt.kubernetes.io/ kubernetes-xenial main" | sudo tee -a /etc/apt/sources.list.d/kubernetes.list sudo apt-get update sudo apt-get install -y kubectl {{< /tab >}} </del> <ins> {{% tab name="Debian-based distributions" %}} 1. Update the `apt` package index and install packages needed to use the Kubernetes `apt` repository: ```shell sudo apt-get update sudo apt-get install -y apt-transport-https ca-certificates curl ``` 2. Download the Google Cloud public signing key: ```shell sudo curl -fsSLo /usr/share/keyrings/kubernetes-archive-keyring.gpg https://packages.cloud.google.com/apt/doc/apt-key.gpg ``` 3. Add the Kubernetes `apt` repository: ```shell echo "deb [signed-by=/usr/share/keyrings/kubernetes-archive-keyring.gpg] https://apt.kubernetes.io/ kubernetes-xenial main" | sudo tee /etc/apt/sources.list.d/kubernetes.list ``` 4. Update `apt` package index with the new repository and install kubectl: ```shell sudo apt-get update sudo apt-get install -y kubectl ``` {{% /tab %}} </ins> <del> {{< tab name="CentOS, RHEL or Fedora" codelang="bash" >}}cat <<EOF > /etc/yum.repos.d/kubernetes.repo </del> <ins> {{< tab name="Red Hat-based distributions" codelang="bash" >}} cat <<EOF > /etc/yum.repos.d/kubernetes.repo </ins> [kubernetes] name=Kubernetes baseurl=https://packages.cloud.google.com/yum/repos/kubernetes-el7-x86_64

Discussion:
The current installation instructions for installing the third party Kubernetes Apt repository on Debian/Ubuntu, goes against best security practice. Currently the signing keys are to . The keychain should be downloaded to (file name to match the name used in ) using or (not as this is deprecated and will be last available in Debian 11 and Ubuntu 22.04) and referred to in as such Page to Update: References:
i read the linked pages and this change seems valid. thank you for bringing this up. would you help us by sending a PR for that? /sig cluster-lifecycle
/priority important-longterm /kind cleanup
/triage accepted
Please see
/sig cli
Change:
title: "弃用 Dockershim 的常见问题" date: 2020-12-02 slug: dockershim-faq <del> aliases: [ '/dockershim' ] </del> --- <!-- layout: blog

Discussion:
This is a Bug Report Problem: The dockershim alias () now directs to the Chinese localized version () because the same alias exists in multiple files. Proposed Solution: Removal of the alias in the Chinese version of the blog post or updated to be A policy or linter might be worth putting in place for aliases as well to prevent future issues. Page to Update:
/triage accepted /kind bug /language zh
A similar problem occurred some time ago with aliases in security. I just checked a few other files. Aliases field is set: content/zh/docs/reference/issues- content/zh/docs/reference/issues- Aliases field not set (set in version): content/zh/docs/reference/access-authn- Should add a note to the localization or documentation about how to update the field.
/assign
Change:
### TaintNodesByCondition {#taintnodesbycondition} <del> {{< feature-state for_k8s_version="v1.12" state="beta" >}} </del> <ins> {{< feature-state for_k8s_version="v1.17" state="stable" >}} </ins> This admission controller {{< glossary_tooltip text="taints" term_id="taint" >}} newly created Nodes as `NotReady` and `NoSchedule`. That tainting avoids a race condition that could cause Pods to be scheduled on new Nodes before their taints were updated to accurately reflect their reported conditions.

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 that the admission controller is beta; however the related feature gate is now GA. Proposed Solution: Verify the feature status of the TaintNodeByCondition feature for the admission controller specifically. If is in fact stable, update the page. Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--Additional Information: /sig node /language en
could you confirm whether that admission controller is still beta?
/triage accepted
/assign
is this just a matter of getting a "yes" from someone on SIG Node to confirm that is GA? It seems to be as you mentioned, since 1.17 () but let me know if we need explicit confirmation and I'll chase it down.
Confirmed GA since 1.17 by Will update the page
Change:
description: > Principles and practices for good RBAC design for cluster operators. content_type: concept <ins> weight: 60 </ins> --- <!-- overview -->

Discussion:
This is a Feature Request What would you like to be A section in the Kubernetes documentation to provide users with best practice guidelines and references to Kubernetes projects and solutions for multi-tenancy. This can be a new section in . Why is this needed Kubernetes is commonly used by multiple teams and to run multiple applications. The has been chartered with defining multi-tenancy models for Kubernetes and making these easy to consume for end users. The group has produced multiple projects like , , and and published blog posts on and the projects (, ). The HNC and Virtual Cluster projects have “graduated” from the working group and are now managed under SIG-auth and SIG-cluster-lifecycle. However, multi-tenancy remains a confusing and complex topic for Kubernetes users, especially beginners. Having a section on multi-tenancy in the Kubernetes documentation, with links to projects, would be helpful to all users. Comments If this seems like a good idea, the Multi-Tenancy WG can take the lead to propose a draft document. cc:
Happy for multitenancy WG to take this forward - also, that WG is welcome to triage this as accepted. Please also explore whether you can put new content within three of the existing sections: and, that way, avoid adding a new section to the concept list - we already have quite a few. of course, it's also fine to add new Task or Reference pages that cover multi-tenancy aspects.
/language en
/triage accepted
See also
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]:
/remove-lifecycle stale
/wg multi-tenancy
The label(s) cannot be applied, because the repository doesn't have them. <detailsIn response to : /wg multi-tenancy 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
/wg multitenancy
Change:
<p>First, check that the app is running. To find the exposed IP address and port, run the <code>describe service</code> command:</p> <p><code><b>kubectl describe services/kubernetes-bootcamp</b></code></p> <p>Create an environment variable called <tt>NODE_PORT</tt> that has the value of the Node port assigned:</p> <del> <p><code><b>export NODE_PORT="$(kubectl get services/kubernetes-bootcamp -o go-template='{{(index .spec.ports 0).nodePort}}')</b></code><br /> </del> <ins> <p><code><b>export NODE_PORT="$(kubectl get services/kubernetes-bootcamp -o go-template='{{(index .spec.ports 0).nodePort}}')"</b></code><br /> </ins> <code><b>echo "NODE_PORT=$NODE_PORT"</b></code></p> <p>Next, do a <code>curl</code> to the the exposed IP and port:</p> <p><code><b>curl http://"$(minikube ip):$NODE_PORT"</b></code></p>

Discussion:
A qotation mark is missing at the end of a command, making it wrong. At the page at step 2: The command is: export NODEPORT="$(kubectl get services/kubernetes-bootcamp -o go-template='{{(index 0).nodePort}}') And should be: export NODEPORT="$(kubectl get services/kubernetes-bootcamp -o go-template='{{(index 0).nodePort}}')"
/language en
/triage accepted
/assign
The label(s) cannot be applied, because the repository doesn't have them. <detailsIn response to : /sig doc </details
Page to Update: /retitle Unquoted export in "Performing a Rolling Update" tutorial /kind bug
This issue has not been updated in over 1 year, and should be re-triaged. You can: Confirm that this issue is still relevant with (org members only) Close this issue with For more details on the triage process, see /remove-triage accepted