jiebi/CodeConvo huggingface dataset:
Change:
is enabled on the API server. An administrator can mark a specific `StorageClass` as default by adding the <del> `storageclass.kubernetes.io/is-default-class` annotation to it. </del> <ins> `storageclass.kubernetes.io/is-default-class` [annotation](/docs/reference/labels-annotations-taints/#storageclass-kubernetes-io-is-default-class) to it. </ins> When a default `StorageClass` exists in a cluster and a user creates a `PersistentVolumeClaim` with `storageClassName` unspecified, the `DefaultStorageClass` admission controller automatically adds the

Discussion:
When enabling dynamic provisioning as default behaviour: It might be helpful to reference the following as a hyper link for clarity
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
/kind feature /language en It sounds as if we could add a hyperlink from to and that would solve it for you Have I got that right?
Hi Tim, I would agree this would be awesome for users. Kind regards Naresh Maharaj
would you be willing to update (edit) the issue description, with in mind, so that it's clear what change you are asking for?
/sig storage
/assign
Change:
db-user-pass-96mffmfh4k          Opaque                                2         51s ``` <ins> You can view a description of the secret: </ins> ```shell kubectl describe secrets/db-user-pass-96mffmfh4k ```

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: Line 355: There is no description before the code. Line 1005: There is no description before the code. Proposed Solution: Line 355: You can view a description of the secret: Line 1005: You can also create a secret for test environment credentials. Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--/language en
/assign
Change:
* start and configure additional etcd instance * configure the {{< glossary_tooltip term_id="kube-apiserver" text="API server" >}} to use it for storing events <del> See [Operating etcd clusters for Kubernetes](https://kubernetes.io/docs/tasks/administer-cluster/configure-upgrade-etcd/) and [Set up a High Availability etcd cluster with kubeadm](docs/setup/production-environment/tools/kubeadm/setup-ha-etcd-with-kubeadm/) </del> <ins> See [Operating etcd clusters for Kubernetes](/docs/tasks/administer-cluster/configure-upgrade-etcd/) and [Set up a High Availability etcd cluster with kubeadm](/docs/setup/production-environment/tools/kubeadm/setup-ha-etcd-with-kubeadm/) </ins> for details on configuring and managing etcd for a large cluster. ## Addon resources

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 href of contains unwanted . A slash () is missing in the href of . Proposed Solution: Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--/language en /assign
/triage accepted
Change:
To configure options for unused container and image garbage collection, tune the kubelet using a [configuration file](/docs/tasks/administer-cluster/kubelet-config-file/) and change the parameters related to garbage collection using the <del> [`KubeletConfiguration`](/docs/reference/config-api/kubelet-config.v1beta1/#kubelet-config-k8s-io-v1beta1-KubeletConfiguration) </del> <ins> [`KubeletConfiguration`](/docs/reference/config-api/kubelet-config.v1beta1/) </ins> resource type. ### Container image lifecycle

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: Url selector #kubelet-config-k8s-io-v1beta1-KubeletConfiguration doesn't make a difference between: and Proposed Solution: Removing the selector from the URLs Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--
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
/assign
/retitle Problems with (generated) reference for kubelet configuration
Change:
[plugins."io.containerd.grpc.v1.cri".containerd.runtimes.${HANDLER_NAME}] ``` <del> containerdの設定に関する詳細なドキュメントは下記を参照してください。 https://github.com/containerd/containerd/blob/main/docs/cri/config.md </del> <ins> 詳細はcontainerdの[設定に関するドキュメント](https://github.com/containerd/containerd/blob/main/docs/cri/config.md)を参照してください。 </ins> #### {{< glossary_tooltip term_id="cri-o" >}}

Discussion:
This is a Feature Request What would you like to be We need to update content/ja/docs/concepts/containers/runtime- according to the English text, because it is outdated. Why is this needed content/ja/docs/concepts/containers/runtime- is outdated. Comments /language ja /assign
/triage accepted
Change:
Information on the different Windows Server servicing channels including their support models can be found at <del> [Windows Server servicing channels](https://docs.microsoft.com/en-us/windows-server/get-started-19/servicing-channels-19). </del> <ins> [Windows Server servicing channels](https://docs.microsoft.com/en-us/windows-server/get-started/servicing-channels-comparison). </ins>

Discussion:
broken link in page:
/kind bug /sig windows /language en /triage accepted /priority backlog Thanks for the report
Would like to work on this issue /assign
Change:
每个 Kubernetes 对象也有一个 [**UID**](#uids) 来标识在整个集群中的唯一性。 比如，在同一个[名字空间](/zh-cn/docs/concepts/overview/working-with-objects/namespaces/) <del> 中有一个名为 `myapp-1234` 的 Pod，但是可以命名一个 Pod 和一个 Deployment 同为 `myapp-1234`。 </del> <ins> 中只能有一个名为 `myapp-1234` 的 Pod，但是可以命名一个 Pod 和一个 Deployment 同为 `myapp-1234`。 </ins> <!-- For non-unique user-provided attributes, Kubernetes provides [labels](/docs/concepts/overview/working-with-objects/labels/) and [annotations](/docs/concepts/overview/working-with-objects/annotations/).

Discussion:
Hello, I found some ambiguity in the Chinese translation of the documentation. In this document() the third line in chinese version is: " myapp-1234 Pod Pod Deployment myapp-1234" And in english version is: "For example, you can only have one Pod named myapp-1234 within the same namespace, but you can have one Pod and one Deployment that are each named myapp-1234." The word "only" is missing in the Chinese version, which will cause ambiguity. Thanks
/language zh /sig documentation
The label(s) cannot be applied, because the repository doesn't have them. <detailsIn response to : /language zh /sig documentation 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
/sig docs
/triage accepted
It seems that there is indeed an ambiguity, we can modify it. /assign
Change:
- DaemonSet controller can make pods even when the scheduler has not been started, which can help cluster bootstrap. <del> Daemon pods do respect [taints and tolerations](/docs/concepts/configuration/assign-pod-node/#taints-and-tolerations-beta-feature), but they are created with `NoExecute` tolerations for the `node.alpha.kubernetes.io/notReady` and `node.alpha.kubernetes.io/unreachable` taints with no `tolerationSeconds`. This ensures that when the `TaintBasedEvictions` alpha feature is enabled, </del> <ins> Daemon pods do respect [taints and tolerations](/docs/concepts/configuration/assign-pod-node/#taints-and-tolerations-beta-feature), but they are created with `NoExecute` tolerations for the following taints with no `tolerationSeconds`: - `node.alpha.kubernetes.io/notReady` - `node.alpha.kubernetes.io/unreachable` - `node.alpha.kubernetes.io/memoryPressure` - `node.alpha.kubernetes.io/diskPressure` When the support to critical pods is enabled and the pods in a DaemonSet are labelled as critical, the Daemon pods are created with an additional `NoExecute` toleration for the `node.alpha.kubernetes.io/outOfDisk` taint with no `tolerationSeconds`. This ensures that when the `TaintBasedEvictions` alpha feature is enabled, </ins> they will not be evicted when there are node problems such as a network partition. (When the `TaintBasedEvictions` feature is not enabled, they are also not evicted in these scenarios, but due to hard-coded behavior of the NodeController rather than due to tolerations).

Discussion:
This is a... <!-- choose one by changing [ ] to [x] --- [ ] Feature Request [x] Bug Report Problem: A DaemonSet by default tolerates not only node ready and node reachability taints. By design, it can tolerate memory pressure and disk pressure taints. For critical pods, it can tolerate outOfDisk taint as well. Proposed Solution: The above mentioned features should be documented. Page to Update:
/assign
Let the doc team know if you require any assistance from SMEs. Since you have assigned the defect to yourself, we assume that you have all the necessary information to fix this issue.
Thanks for the heads up. The source code (and comment) is already telling us what were missing.
Change:
<ins> --- title: Watch id: watch date: 2024-07-02 full_link: /docs/reference/using-api/api-concepts/#api-verbs short_description: > A verb that is used to track changes to an object in Kubernetes as a stream. aka: tags: - API verb - fundamental --- A verb that is used to track changes to an object in Kubernetes as a stream. It is used for the efficient detection of changes. <!--more--> A verb that is used to track changes to an object in Kubernetes as a stream. Watches allow efficient detection of changes; for example, a {{< glossary_tooltip term_id="controller" text="controller">}} that needs to know whenever a ConfigMap has changed can use a watch rather than polling. See [Efficient Detection of Changes in API Concepts](/docs/reference/using-api/api-concepts/#efficient-detection-of-changes) for more information. </ins>

Discussion:
This is a Feature Request <!-- Please only use this template for submitting feature/enhancement requests --<!-- See for guidance on writing an actionable issue description. --What would you like to be Update the to include an explanation of “watch”. Why is this needed The watch verb (and actually watchcollection as well) is K8s-specific jargon. We should help readers understand it. Comments Extra credit for also using the new term in existing pages, using a . /kind feature /wg api-expression
/assign
/priority backlog /triage accepted
Hi PR: for this issue. PTAL
I'm happy for any reviewer (for English) to take a look there.
Change:
### Linux ```shell <del> export KUBECONFIG=$KUBECONFIG:config-demo:config-demo-2 </del> <ins> export KUBECONFIG="${KUBECONFIG}:config-demo:config-demo-2" </ins> ``` ### Windows PowerShell

Discussion:
Setting KUBECONFIG variable doesn't work very well on macOS (Monterey 12.2.1). In the line: The first colon (:) will make the following character (c) dissappear: What I get is the mangled text: What works for me better is explicitly using full paths:
This issue is currently awaiting triage. SIG Docs takes a lead on issue triage for this website, but any Kubernetes member can accept issues by applying the label. The label can be by org members by writing in a comment. <detailsInstructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details
The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs. This bot triages issues and PRs according to the following rules: After 90d of inactivity, is applied After 30d of inactivity since was applied, is applied After 30d of inactivity since was applied, the issue is closed You can: Mark this issue or PR as fresh with Mark this issue or PR as rotten with Close this issue or PR with Offer to help out with [Issue Triage][1] Please send feedback to sig-contributor-experience at . /lifecycle stale [1]:
Thanks for reporting, I can open a PR to fix this! /remove-lifecycle stale /assign
Change:
the nodes, managing the pods and containers running on a machine. The kubelet translates each pod into its constituent containers and fetches individual container usage statistics from the container runtime through the container <del> runtime interface. The kubelet fetches this information from the integrated cAdvisor for the legacy Docker integration.  It then exposes the aggregated pod </del> <ins> runtime interface. If you use a container runtime that uses Linux cgroups and namespaces to implement containers, and the container runtime does not publish usage statistics, then the kubelet can look up those statistics directly (using code from [cAdvisor](https://github.com/google/cadvisor)). No matter how those statistics arrive, the kubelet then exposes the aggregated pod </ins> resource usage statistics through the metrics-server Resource Metrics API. This API is served at `/metrics/resource/v1beta1` on the kubelet's authenticated and read-only ports.

Discussion:
Umbrella issue Fixes issue File: /tasks/debug-application-cluster/resource-usage- URL: Line 44 mentions how the kubelet pulls info for Docker integration for metrics-server. Action: Review to see if it works as intended in a world without dockershim. File: /tasks/debug-application-cluster/debug-application- URL: Line 106 and other output examples use docker as the runtime. Action: Reproduce the output samples on a cluster not running Docker and update the samples. kubernetes/website/content/en/docs/tasks/debug-application- File: /tasks/debug-application- URL: Line 103 mentions specifying the Docker version when filing a Github issue. Action: Say instead to mention the runtime and version being used. File: /tasks/debug-application-cluster/debug- URL: Line 679 has . Action: Reproduce using a different runtime and update. /sig docs /language en
I'm tempted to move to a new page in the reference section, that we insta-deprecate (removal in, say, v1.27). How does that sound?
Agreed /assign
Are you covering everything listed in this issue? If so, I'd like to move this from backlog to in-flight in the dockershim project board, so nobody else tries to work on this.
yes, thank you!
/triage accepted
Is everything listed in the first entry done? What's left, if anything?
cc
Yes it is, I'm waiting for my PR in kubernetes/cri-tools to get merged before I close that one :)
URL: I don't think this needs to change tbh, since it's a very generic example.
/milestone 1.24
Dockershim removal work is ongoing, clearing the 1.24 milestone. This can be to subsequent milestones if needed. /milestone clear
Change:
<ins> apiVersion: v1 kind: Pod metadata: name: configmap-demo-pod spec: containers: - name: demo image: alpine command: ["sleep", "3600"] env: # Define the environment variable - name: PLAYER_INITIAL_LIVES # Notice that the case is different here # from the key name in the ConfigMap. valueFrom: configMapKeyRef: name: game-demo           # The ConfigMap this value comes from. key: player_initial_lives # The key to fetch. - name: UI_PROPERTIES_FILE_NAME valueFrom: configMapKeyRef: name: game-demo key: ui_properties_file_name volumeMounts: - name: config mountPath: "/config" readOnly: true volumes: # You set volumes at the Pod level, then mount them into containers inside that Pod - name: config configMap: # Provide the name of the ConfigMap you want to mount. name: game-demo # An array of keys from the ConfigMap to create as files items: - key: "game.properties" path: "game.properties" - key: "user-interface.properties" path: "user-interface.properties" </ins>  No newline at end of file

Discussion:
We can, and should, update the example that appears after We can make this use the shortcode - see Whenever we give examples that the reader could try out by running them, we should prefer using shortcodes.
/language en /triage accepted I recommend switching it to a shortcode per
I'm not sure that there's anything actually wrong with the of that Pod, though. /kind cleanup
Pasting that snippet into my own code gave me errors and it took me some time to figure out that it was due to the copied code being incorrect.
would you be willing to provide a diff for that manifest that shows the fix? It'd help.
Here is what it is currently: and here's how it should be. It's actually and everything within that block that should be shift-tab'd. There's another example on that page which is correct and you can find it by searching for "name: foo"
/assign
Change:
An example is an existing application that assumes a particular well-known environment variable holds a unique identifier. One possibility is to wrap the <del> application, but that is tedious and error prone, and it violates the goal of low </del> <ins> application, but that is tedious and error-prone, and it violates the goal of low </ins> coupling. A better option would be to use the Pod's name as an identifier, and inject the Pod's name into the well-known environment variable.

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 downward API page writes “error prone”, where “error-prone” would send a much more clear context signal to localization teams. Proposed Solution: Add the missing character. The page was recently updated so no other changes are needed; however, it would super useful to include the other fix from The other change is to remove the parens around: (from the same page!) Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--Additional Information: /kind cleanup /language en /good-first-issue /priority backlog /triage accepted
This request has been marked as suitable for new contributors. 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 : This is a Bug Report <!-- See for guidance on writing an actionable issue description. --Problem: The downward API page writes “error prone”, where “error-prone” would send a much more clear context signal to localization teams. Add the missing character. The page was recently updated so no other changes are needed; however, it would super useful to include the other fix from The other change is to remove the parens around: based on the calculation <!--Kubernetes Version:--/kind cleanup /language en /good-first-issue /priority backlog /triage accepted </details
/assign
Change:
- proxy to target may use HTTP or HTTPS as chosen by proxy using available information - can be used to reach a Node, Pod, or Service - does load balancing when used to reach a Service 1. The [kube proxy](/docs/concepts/services-networking/service/#ips-and-vips): - runs on each node - proxies UDP and TCP - does not understand HTTP - provides load balancing - is just used to reach services 1. A Proxy/Load-balancer in front of apiserver(s): - existence and implementation varies from cluster to cluster (e.g. nginx) - sits between all clients and one or more apiservers - acts as load balancer if there are several apiservers. 1. Cloud Load Balancers on external services: - are provided by some cloud providers (e.g. AWS ELB, Google Cloud Load Balancer) - are created automatically when the Kubernetes service has type `LoadBalancer` - use UDP/TCP only

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 bullet points nested under numbered list aren't rendered as bulleted list: <img width="869" alt="screen shot 2017-06-10 at 2 15 49 pm" src="https://user-"Proposed Solution: Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--
The sub-link isn't correct either. For example, kubectl proxy links to but should instead link to I guess it's because is split from () /assign
Change:
```shell docker build -t gcr.io/PROJECT_ID/hello-node:v2 . <del> docker push gcr.io/PROJECT_ID/hello-node:v2 </del> <ins> gcloud docker push gcr.io/PROJECT_ID/hello-node:v2 </ins> ``` Building and pushing this updated image should be much quicker as we take full advantage of the Docker cache.

Discussion:
In issuing the push to in the "Rolling Updates" section: docker push read: gcloud docker push
PR submitted:
cc
Thanks, Al; confirmed that is the command by talking to the GCR team today.
Change:
/docs/admin/     /docs/concepts/cluster-administration/cluster-administration-overview/ 301 /docs/admin/add-ons/     /docs/concepts/cluster-administration/addons/ 301 <ins> /docs/admin/addons/     /docs/concepts/cluster-administration/addons/ 301 </ins> /docs/admin/apparmor/     /docs/tutorials/clusters/apparmor/ 301 /docs/admin/audit/     /docs/tasks/debug-application-cluster/audit/ 301 /docs/admin/authorization/rbac.md     /docs/admin/authorization/rbac/ 301

Discussion:
<!--Required Information--This is a... <!-- choose one by changing [ ] to [x] --- [ ] Feature Request [x] Bug Report Problem: The above wiki and mentions an invalid URL Browsing to results in URL 404 Error Proposed Solution: Update url on the wiki and in output Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--
thanks Looks like we need a redirect for that gets to the right end destintation (which I think is has moved to )