jiebi/CodeConvo huggingface dataset:
Code change:
<ins> --- title: Event id: event date: 2022-01-16 full_link: /docs/reference/kubernetes-api/cluster-resources/event-v1/ short_description: > A report of an event somewhere in the cluster. It generally denotes some state change in the system. aka: tags: - core-object - fundamental --- Each Event is a report of an event somewhere in the {{< glossary_tooltip text="cluster" term_id="cluster" >}}. It generally denotes some state change in the system. <!--more--> Events have a limited retention time and triggers and messages may evolve with time. Event consumers should not rely on the timing of an event with a given reason reflecting a consistent underlying trigger, or the continued existence of events with that reason. Events should be treated as informative, best-effort, supplemental data. In Kubernetes, [auditing](/docs/tasks/debug-application-cluster/audit/) generates a different kind of Event record (API group `audit.k8s.io`). </ins>

Related discussion:
text: This is an Enhancement 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 "event" entry to the Kubernetes . Why is this needed s are referenced several times in other definitions, but it is not itself defined.
Caution for people working on this: there is an API in and there is also an audit Event type in . The glossary entry should help readers who are confused between the two /language en /triage accepted
/assign I would like to work on this
Awesome, thanks
Code change:
to be pulled, then the kubelet will try to download them from both authentication sources if one of them fails. ### Pre-pulled images {{< note >}}

Related discussion:
text: Ref: needs a rewrite. It mentions Docker (and Podman!) all over the place, which is a good indication that the docs are old enough to need a rewrite. At a minimum, remove mentions of Docker in these topics: /triage accepted /milestone 1.24
/assign
/assign
Reasked folks in Slack for correct disposition
Asked in the SIG Node slack channel:
To summarize the consensus from talking with folks about this issue, specifically the examples in Using a Private Registry section: The steps in the Using a Private Registry section are still valid. However, as written, it makes it sound like Docker is the only/recommended way to do this-which we dont want. We should be able to remove the docker examples and point folks to this page , which covers most of the same content with third party disclaimers already written into the examples. I plan to open a PR later this week with these changes!
Has anyone opened a PR for this issue? It seems to be referring to
Code change:
The {{< api-reference page="workload-resources/pod-v1" >}} object definition describes the object in detail. * [The Distributed System Toolkit: Patterns for Composite Containers](/blog/2015/06/the-distributed-system-toolkit-patterns/) explains common layouts for Pods with more than one container. <del> * Read about [Pod topology spread constraints](/docs/concepts/workloads/pods/pod-topology-spread-constraints/). </del> <ins> * Read about [Pod topology spread constraints](/docs/concepts/scheduling-eviction/topology-spread-constraints//). </ins> --> * 了解 [Pod 生命周期](/zh-cn/docs/concepts/workloads/pods/pod-lifecycle/)。 * 了解 [RuntimeClass](/zh-cn/docs/concepts/containers/runtime-class/)，以及如何使用它

Related discussion:
text: This is a Feature Request Will relocate this file from to in which may involve some text updates and link fix.
/triage accepted
/language zh
/assign
/assign I handle the language/zh-cn
Regarding assignee issue I share the following comment in the releated PR. :)
Yes, this is not a simple relocation, which involves with much localization of new paras and text.
Code change:
(and the default interval is 15 seconds). Once during each period, the controller manager queries the resource utilization against the <del> metrics specified in each HorizontalPodAutoscaler definition.  The controller manager obtains the metrics from either the resource metrics API (for per-pod resource metrics), </del> <ins> metrics specified in each HorizontalPodAutoscaler definition.  The controller manager finds the target resource defined by the `scaleTargetRef`, then selects the pods based on the target resource's `.spec.selector` labels, and obtains the metrics from either the resource metrics API (for per-pod resource metrics), </ins> or the custom metrics API (for all other metrics). * For per-pod resource metrics (like CPU), the controller fetches the metrics

Related discussion:
text: I created a new deployment "mydeploy-dotnetcounters" with two containers, one with resource request and limit set and one without. The new deployment had these labels: The HPA for a different deployment "mydeploy" started to fail with: The "mydeploy" deployment had these labels: I resource request and limit to the second container in the "mydeploy-dotnetcounters" deployment and the HPA for "mydeploy" recovered. It seems that the HPA decide what pod to check based on what labels match. However these is no mention of that mechanism in the HPA documentation ( that I could find ). Not here: And not here: I expect the HPA for one deployment to not be affected by the configuration of another deployment. I expect that I can read about the mechanism by which an HPA decides which pods' metrics to examine. Create a deployment with an HPA. Create a second deployment that is a clone of the first, but with an additional label and with resource request cpu not set. No response <details</details<detailsGKE v1.20.11-gke.1300 </details<details</details<details</details<details</details<details</details
This issue is currently awaiting triage. If a SIG or subproject determines this is a relevant issue, they will accept it by applying the label and provide further guidance. 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
/sig docs
/sig autoscaling
This really belongs in the repo /transfer website
/language en /triage accepted /priority backlog /kind feature Thanks for the suggestion
/assign
Code change:
--- <del> title: Node </del> <ins> title: Nó </ins> id: node date: 2020-04-19 full_link: /docs/concepts/architecture/nodes/ short_description: > <del> Um Node é uma máquina de trabalho no Kubernetes. </del> <ins> Um Nó é uma máquina de trabalho no Kubernetes. </ins> aka: tags: - fundamental --- <del> Um Node é uma máquina de trabalho no Kubernetes. </del> <ins> Um Nó é uma máquina de trabalho no Kubernetes. </ins> <!--more--> <del> Um Node pode ser uma máquina virtual ou física, dependendo do cluster. Possui daemons ou serviços locais necessários para executar {{< glossary_tooltip text="Pods" term_id="pod" >}} e é gerenciado pelo {{< glossary_tooltip text="plano de controle" term_id="control-plane" >}}. Os daemons em um Node incluem  {{< glossary_tooltip text="kubelet" term_id="kubelet" >}}, {{< glossary_tooltip text="kube-proxy" term_id="kube-proxy" >}} e um contêiner runtime implementando o {{< glossary_tooltip text="CRI" term_id="cri" >}} como por exemplo o {{< glossary_tooltip term_id="docker" >}}. </del>  No newline at end of file <ins> Um Nó pode ser uma máquina virtual ou física, dependendo do cluster. Possui daemons ou serviços locais necessários para executar {{< glossary_tooltip text="Pods" term_id="pod" >}} e é gerenciado pelo {{< glossary_tooltip text="ambiente de gerenciamento" term_id="control-plane" >}}. Os daemons em um Node incluem  {{< glossary_tooltip text="kubelet" term_id="kubelet" >}}, {{< glossary_tooltip text="kube-proxy" term_id="kube-proxy" >}} e um contêiner runtime implementando o {{< glossary_tooltip text="CRI" term_id="cri" >}} como por exemplo o {{< glossary_tooltip term_id="docker" >}}. </ins>  No newline at end of file

Related discussion:
text: 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: is giving 404 Proposed Solution: if doesn't have the pt version Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--
/assign
Code change:
replace `<image-name>:<tag>` with `<image-name>@<digest>` (for example, `image@sha256:45b23dee08af5e43a7fea6c4cf9c25ccf269ee113168c19722f87876677c5cb2`). <del> When using image tags, if the image registry were to change the code that the tag on that image represents, you might end up with a mix of Pods running the old and new code. An image digest uniquely identifies a specific version of the image, so Kubernetes runs the same code every time it starts a container with that image name and digest specified. Specifying an image fixes the code that you run so that a change at the registry cannot lead to that mix of versions. </del> <ins> When using image tags, if the image registry were to change the code that the tag on that image represents, you might end up with a mix of Pods running the old and new code. An image digest uniquely identifies a specific version of the image, so Kubernetes runs the same code every time it starts a container with that image name and digest specified. Specifying an image by digest fixes the code that you run so that a change at the registry cannot lead to that mix of versions. </ins> There are third-party [admission controllers](/docs/reference/access-authn-authz/admission-controllers/) that mutate Pods (and pod templates) when they are created, so that the

Related discussion:
text: Ref: needs a rewrite. It mentions Docker (and Podman!) all over the place, which is a good indication that the docs are old enough to need a rewrite. At a minimum, remove mentions of Docker in these topics: /triage accepted /milestone 1.24
/assign
/assign
Reasked folks in Slack for correct disposition
Asked in the SIG Node slack channel:
To summarize the consensus from talking with folks about this issue, specifically the examples in Using a Private Registry section: The steps in the Using a Private Registry section are still valid. However, as written, it makes it sound like Docker is the only/recommended way to do this-which we dont want. We should be able to remove the docker examples and point folks to this page , which covers most of the same content with third party disclaimers already written into the examples. I plan to open a PR later this week with these changes!
Has anyone opened a PR for this issue? It seems to be referring to
Code change:
$($(CertUtil -hashfile .kubectl-convert.exe SHA256)[1] -replace " ", "") -eq $(type .kubectl-convert.exe.sha256) ``` <del> 1. Append or prepend the kubectl binary folder to your `PATH` environment variable. </del> <ins> 1. Append or prepend the `kubectl-convert` binary folder to your `PATH` environment variable. </ins> 1. Verify plugin is successfully installed

Related discussion:
text: 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 , the step No. 3 is talking about the location of binary, but actually in this section ("Install plugin") we should care about the location of binary, not of binary. Proposed Solution: In : And optionally, wrap these words with backquotes in : : kubectl L47: kubectl L62: kubectl L159: kubectl-convert L165: kubectl-convert (L180: kubectl-convert) - Already suggested above. Page to Update: )-,Append%20or%20prepend%20the%20kubectl%20binary%20folder%20to%20your%20PATH%20environment%20variable.,-Verify%20plugin%20is <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--
/language en
/triage accepted
/assign
Code change:
* Node: A single virtual or physical machine in a Kubernetes cluster. * Cluster: A group of nodes firewalled from the internet, that are the primary compute resources managed by Kubernetes. * Edge router: A router that enforces the firewall policy for your cluster. This could be a gateway managed by a cloudprovider or a physical piece of hardware. <del> * Cluster network: A set of links, logical or physical, that facilitate communication within a cluster according to the [Kubernetes networking model](https://github.com/kubernetes/kubernetes/blob/release-1.0/docs/admin/networking.md). Examples of a Cluster network include Overlays such as [flannel](https://github.com/coreos/flannel#flannel) or SDNs such as [OVS](https://github.com/kubernetes/kubernetes/blob/release-1.0/docs/admin/ovs-networking.md). * Service: A Kubernetes [Service](https://github.com/kubernetes/kubernetes/blob/release-1.0/docs/user-guide/services.md) that identifies a set of pods using label selectors. Unless mentioned otherwise, Services are assumed to have virtual IPs only routable within the cluster network. </del> <ins> * Cluster network: A set of links, logical or physical, that facilitate communication within a cluster according to the [Kubernetes networking model](/docs/admin/networking/). Examples of a Cluster network include Overlays such as [flannel](https://github.com/coreos/flannel#flannel) or SDNs such as [OVS](/docs/admin/ovs-networking/). * Service: A Kubernetes [Service](/docs/user-guide/services/) that identifies a set of pods using label selectors. Unless mentioned otherwise, Services are assumed to have virtual IPs only routable within the cluster network. </ins> ## What is Ingress?

Related discussion:
text: <!-- 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: Links in the Terminology section point to (obsolete?) documents. Proposed Solution: Point them at master. Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--
thanks! Addressed in PR
Code change:
<!--more--> <!-- <del> [Pod Priority](/docs/concepts/configuration/pod-priority-preemption/#pod-priority) gives the ability to set scheduling priority of a Pod to be higher and lower than other Pods — an important feature for production clusters workload. </del> <ins> [Pod Priority](/docs/concepts/scheduling-eviction/pod-priority-preemption/#pod-priority) gives the ability to set scheduling priority of a Pod to be higher and lower than other Pods — an important feature for production clusters workload. </ins> --> <del> [Pod 优先级](/zh/docs/concepts/configuration/pod-priority-preemption/#pod-priority) </del> <ins> [Pod 优先级](/zh/docs/concepts/scheduling-eviction/pod-priority-preemption/#pod-priority) </ins> 允许用户为 Pod 设置高于或低于其他 Pod 的优先级 -- 这对于生产集群 工作负载而言是一个重要的特性。

Related discussion:
text: There is a bug: ,%E8%AE%BE%E4%B8%BA%20%2D997%E3%80%82 ""'s hyperlink status is 404, it should be changed to ""
This issue is currently awaiting triage. SIG Docs takes a lead on issue triage for this website, but any Kubernetes member can accept issues by applying the label. The label can be by org members by writing in a comment. <detailsInstructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details
/language zh /kind bug
/assign
Code change:
<ins> --- title: Container Environment content_type: concept weight: 20 --- <!-- overview --> Questa pagina descrive le risorse disponibili nei Container eseguiti in Kubernetes. <!-- body --> ## Container environment Quando si esegue un Container in Kubernetes, le seguenti risorse sono rese disponibili: * Un filesystem, composto dal file system dell'[image](/docs/concepts/containers/images/) e da uno o più [volumes](/docs/concepts/storage/volumes/). * Una serie di informazioni sul Container stesso. * Una serie di informazioni sugli oggetti nel cluster. ### Informazioni sul Container L' *hostname* di un Container è il nome del Pod all'interno del quale è eseguito il Container. È consultabile tramite il comando `hostname` o tramite la funzione [`gethostname`](http://man7.org/linux/man-pages/man2/gethostname.2.html) disponibile in libc. Il nome del Pod e il namespace possono essere resi disponibili come environment variables attraverso l'uso delle [downward API](/docs/tasks/inject-data-application/downward-api-volume-expose-pod-information/). Gli utenti possono aggiungere altre environment variables nella definizione del Pod; anche queste saranno disponibili nel Container come tutte le altre environment variables definite staticamente nella Docker image. ### Informazioni sul cluster Al momento della creazione del Container è generata una serie di environment variables con la lista di servizi in esecuzione nel cluster. Queste environment variables rispettano la sintassi dei Docker links. Per un servizio chiamato *foo* che è in esecuzione in un Container di nome *bar*, le seguenti variabili sono generate: ```shell FOO_SERVICE_HOST=<host su cui il servizio è attivo> FOO_SERVICE_PORT=<porta su cui il servizio è pubblicato> ``` I servizi hanno un indirizzo IP dedicato e sono disponibili nei Container anche via DNS se il [DNS addon](http://releases.k8s.io/{{< param "githubbranch" >}}/cluster/addons/dns/) è installato nel cluster. ## {{% heading "whatsnext" %}} * Approfondisci [Container lifecycle hooks](/docs/concepts/containers/container-lifecycle-hooks/). * Esegui un tutorial su come [definire degli handlers per i Container lifecycle events](/docs/tasks/configure-pod-container/attach-handler-lifecycle-event/). </ins>

Related discussion:
text: I would like to have the "Container Environment" page to be translated into Italian page /language it /priority important-soon
/assign /lifecycle active
Code change:
## Memory QoS with cgroup v2 <del> {{< feature-state feature-gate-name="MemoryQoS" >}} </del> <ins> {{< feature-state feature_gate_name="MemoryQoS" >}} </ins> Memory QoS uses the memory controller of cgroup v2 to guarantee memory resources in Kubernetes. Memory requests and limits of containers in pod are used to set specific interfaces `memory.min`

Related discussion:
text: FEATURE STATE for feature says According to page it is still alpha, being first introduced in 1.22. Should not the FEATURE STATE line then say ?
Page related to issue: /language en
/retitle Empty feature state tag for "Memory QoS with cgroup v2" in "Pod Quality of Service Classes" page /kind bug
We should fix so that the correct feature state is reflected. /priority backlog /triage accepted
It appears that resolving this issue is straightforward. Simply updating the shortcode parameter in will ensure that the correct feature state is reflected accurately. Thanks for bringing this to our attention! /help
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 : It appears that resolving this issue is straightforward. Simply updating the shortcode parameter in will ensure that the correct feature state is reflected accurately. Thanks for bringing this to our attention! /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
I will want help with this. /assign
Code change:
- The ConfigMap parameters for the kube-proxy cannot all be validated and verified on startup.  For example, if your operating system doesn't allow you to run iptables commands, the standard kernel kube-proxy implementation will not work.  Likewise, if you have an operating system which doesn't support `netsh`, it will not run in Windows userspace mode. ### User space proxy mode {#proxy-mode-userspace} <ins> {{< feature-state for_k8s_version="v1.23" state="deprecated" >}} </ins> In this (legacy) mode, kube-proxy watches the Kubernetes control plane for the addition and removal of Service and Endpoint objects. For each Service it opens a

Related discussion:
text: 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: marks the userspace kube-proxy as deprecated. This was missed from the v1.23 docs updates and . Proposed Solution: Mark the kube-proxy in userspace mode as deprecated. Page to Update: <!--Additional Information:--/sig network /language en /priority important-longterm
/lifecycle frozen /triage accepted
/assign
Code change:
<ins> --- title: 垃圾收集 id: garbage-collection date: 2021-07-07 full_link: /zh/docs/concepts/workloads/controllers/garbage-collection/ short_description: > Kubernetes 用于清理集群资源的各种机制的统称。 aka: tags: - fundamental - operation --- <!-- title: Garbage Collection id: garbage-collection date: 2021-07-07 full_link: /docs/concepts/workloads/controllers/garbage-collection/ short_description: > A collective term for the various mechanisms Kubernetes uses to clean up cluster resources. aka: tags: - fundamental - operation --> <!-- Garbage collection is a collective term for the various mechanisms Kubernetes uses to clean up cluster resources. --> 垃圾收集是 Kubernetes 用于清理集群资源的各种机制的统称。 <!--more--> <!-- Kubernetes uses garbage collection to clean up resources like [unused containers and images](/docs/concepts/workloads/controllers/garbage-collection/#containers-images), [failed Pods](/docs/concepts/workloads/pods/pod-lifecycle/#pod-garbage-collection), [objects owned by the targeted resource](/docs/concepts/overview/working-with-objects/owners-dependents/), [completed Jobs](/docs/concepts/workloads/controllers/ttlafterfinished/), and resources that have expired or failed. --> Kubernetes 使用垃圾收集机制来清理资源，例如： [未使用的容器和镜像](/zh/docs/concepts/workloads/controllers/garbage-collection/#containers-images)、 [失败的 Pod](/zh/docs/concepts/workloads/pods/pod-lifecycle/#pod-garbage-collection)、 [目标资源拥有的对象](/zh/docs/concepts/overview/working-with-objects/owners-dependents/)、 [已完成的 Job](/zh/docs/concepts/workloads/controllers/ttlafterfinished/)、 过期或出错的资源。 </ins>  No newline at end of file

Related discussion:
text: This is a Feature Request translate docs/reference/glossary/garbage- into Chinese. What would you like to be content/zh/docs/reference/glossary/garbage- /language zh /assign
/triage accepted