jiebi/CodeConvo huggingface dataset:
Change:
That page does not render well in my Chrome and Microsoft Edge browser. I guess there is a small typo somewhere. I see it as very wide page.
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
OMG I see now it is because of the too long and Well that makes it really not so nice to look at. I guess you can easily improve on that ;-)

Discussion:
} body { <del> display: grid; grid-column-template: auto; </del> header + .td-outer { min-height: 50vh; height: auto;
Change:
This page has some HTML formatting issues. To see content we have to scroll right. Would you please check
This issue is currently awaiting triage. SIG Docs takes a lead on issue triage for this website, but any Kubernetes member can accept issues by applying the label. The label can be by org members by writing in a comment. <detailsInstructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details
/language en
/sig docs /area web-development

Discussion:
} body { <del> display: grid; grid-column-template: auto; </del> header + .td-outer { min-height: 50vh; height: auto;
Change:
deployment does not exist
/retitle [zh] Issue with
/triage accepted /language zh
In English page, the links goes to
/assign
The reason is that the Chinese version link is not synchronized with the English version. However, when I synchronized the pipeline page, I found that there was a problem with other content that needed to be synchronized , and I needed to wait for this issue to be solved before I could synchronize.

Discussion:
是集群范围资源用量数据的聚合器。 默认情况下，在由 `kube-up.sh` 脚本创建的集群中会以 Deployment 的形式被部署。 如果你使用其他 Kubernetes 安装方法，则可以使用提供的 <del> [部署组件 components.yaml](https://github.com/kubernetes-incubator/metrics-server/tree/master/deploy) </del> <ins> [部署组件 components.yaml](https://github.com/kubernetes-sigs/metrics-server/releases) </ins> 来部署。 <!--
Change:
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 Mention kui within Why is this needed We should make the tool more prominent. Comments Based on an idea from /kind feature /triage accepted /language en /priority backlog
I would make this change by editing and adding a new entry that describes kui. /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 : I would make this change by editing and adding a new entry that describes kui. /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
/sig cli
Hi , I would like to work on this issue. /assign
I have one question: While describing about about kui, should I also include some of its uses?

Discussion:
* Translate a Docker Compose file into Kubernetes objects * Go from local Docker development to managing your application via Kubernetes * Convert v1 or v2 Docker Compose `yaml` files or [Distributed Application Bundles](https://docs.docker.com/compose/bundles/) <ins> ## Kui [`Kui`](https://github.com/kubernetes-sigs/kui) is a GUI tool that takes your normal `kubectl` command line requests and responds with graphics. Kui takes the normal `kubectl` command line requests and responds with graphics. Instead of ASCII tables, Kui provides a GUI rendering with tables that you can sort. Kui lets you: * Directly click on long, auto-generated resource names instead of copying and pasting * Type in `kubectl` commands and see them execute, even sometimes faster than `kubectl` itself * Query a {{< glossary_tooltip text="Job" term_id="job">}} and see its execution rendered as a waterfall diagram * Click through resources in your cluster using a tabbed UI </ins>  No newline at end of file
Change:
This is a Feature Request <!-- Please only use this template for submitting feature/enhancement requests --<!-- See for guidance on writing an actionable issue description. --What would you like to be <!-- Describe as precisely as possible how this feature/enhancement should work from the user perspective. What should be changed, etc. --Apply the change which was by to Japanese website. Why is this needed The change which was by is not applied to Japanese page yet. Comments <!-- Any additional related comments that might help. Drawings/mockups would be extremely helpful (if required). --/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

Discussion:
アクセスモードは次の通りです。 <del> * ReadWriteOnce –ボリュームは単一のNodeで読み取り/書き込みとしてマウントできます * ReadOnlyMany –ボリュームは多数のNodeで読み取り専用としてマウントできます * ReadWriteMany –ボリュームは多数のNodeで読み取り/書き込みとしてマウントできます </del> <ins> `ReadWriteOnce` : ボリュームは単一のNodeで読み取り/書き込みとしてマウントできます `ReadOnlyMany` : ボリュームは多数のNodeで読み取り専用としてマウントできます `ReadWriteMany` : ボリュームは多数のNodeで読み取り/書き込みとしてマウントできます `ReadWriteOncePod` : ボリュームは、単一のPodで読み取り/書き込みとしてマウントできます。クラスタ全体で1つのPodのみがそのPVCの読み取りまたは書き込みを行えるようにする場合は、ReadWriteOncePodアクセスモードを使用します。これは、CSIボリュームとKubernetesバージョン1.22以降でのみサポートされます。 これについてはブログ[Introducing Single Pod Access Mode for PersistentVolumes](/blog/2021/09/13/read-write-once-pod-access-mode-alpha/)に詳細が記載されています。 </ins> CLIではアクセスモードは次のように略されます。
Change:
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: Kubernetes sets an annotation, . However, this annotation is not registered / documented. Proposed Solution: Add that annotation to . There is also a deprecated beta annotation, ; register / document that, and mark it as deprecated. Page to Update: Additional Information: /sig storage /language en /priority backlog and may provide some context for this.
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 I would like to work on this

Discussion:
If `PersistentVolumeLabel` does not support automatic labeling of your PersistentVolumes, you should consider adding the labels manually (or adding support for `PersistentVolumeLabel`). With `PersistentVolumeLabel`, the scheduler prevents Pods from mounting volumes in a different zone. If your infrastructure doesn't have this constraint, you don't need to add the zone labels to the volumes at all. <ins> ## volume.beta.kubernetes.io/storage-provisioner (deprecated) Example: `volume.beta.kubernetes.io/storage-provisioner: k8s.io/minikube-hostpath` Used on: PersistentVolumeClaim This annotation has been deprecated. ## volume.kubernetes.io/storage-provisioner Used on: PersistentVolumeClaim This annotation will be added to dynamic provisioning required PVC. </ins> ## node.kubernetes.io/windows-build {#nodekubernetesiowindows-build} Example: `node.kubernetes.io/windows-build=10.0.17763`
Change:
Kubernetes manages the lifecycle of all images through its image manager, which is part of the kubelet, with the cooperation of cadvisor. Needs pop up note on cadvisor
/kind feature /language en I think by pop up note, you're talking about a . Good suggestion, thanks! To fix this, someone should: add a new glossary entry read for context look in copy an existing item to use as a template (make sure to change everything that needs changing) add a glossary tooltip for cadvisor to /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 : /kind feature /language en add a new glossary entry /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
/priority backlog

Discussion:
### Container image lifecycle Kubernetes manages the lifecycle of all images through its *image manager*, <del> which is part of the kubelet, with the cooperation of cadvisor. The kubelet </del> <ins> which is part of the kubelet, with the cooperation of {{< glossary_tooltip text="cadvisor" term_id="cadvisor" >}}. The kubelet </ins> considers the following disk usage limits when making garbage collection decisions:

<ins> --- title: cAdvisor id: cadvisor date: 2021-12-09 full_link: https://github.com/google/cadvisor/ short_description: > Tool that provides understanding of the resource usage and perfomance characteristics for containers aka: tags: - tool --- cAdvisor (Container Advisor) provides container users an understanding of the resource usage and performance characteristics of their running {{< glossary_tooltip text="containers" term_id="container" >}}. <!--more--> It is a running daemon that collects, aggregates, processes, and exports information about running containers. Specifically, for each container it keeps resource isolation parameters, historical resource usage, histograms of complete historical resource usage and network statistics. This data is exported by container and machine-wide. </ins>
Change:
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 yaml for control-plane-flags patch section has an incorrect structure. Please see the InitConfiguration definition here: Proposed Solution: It should be like this: Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--23 <!--Additional Information:--
I'd prepare a PR on this, but cloning the repo takes forever. Will do that tomorrow.
That is indeed a bug in the docs. Thanks for logging the ticket. /assign /sig cluster-lifecycle
i can send the PR, but if you'd like to contribute in the future you must also sign the CLA.
Sure thing. Will do! Thanks for the heads up!
PR is up /triage accepted

Discussion:
```yaml apiVersion: kubeadm.k8s.io/v1beta3 kind: InitConfiguration <del> nodeRegistration: patches: directory: /home/user/somedir </del> <ins> patches: directory: /home/user/somedir </ins> ``` {{< note >}}

```yaml apiVersion: kubeadm.k8s.io/v1beta3 kind: JoinConfiguration <del> nodeRegistration: patches: directory: /home/user/somedir </del> <ins> patches: directory: /home/user/somedir </ins> ``` The directory must contain files named `target[suffix][+patchtype].extension`.
Change:
URL: File: /tasks/inject-data-application/define-command-argument- Remove the entire Notes section. Clean up the page so that there's no mention of a specific runtime. /sig docs /language en
I would remove the entire section. Docker is far from the only alternative to Kubernetes. If someone wanted to, we could accept a blog article that compares Docker, Kubernetes, Nomad, etc for how you specify these things. But it's fine if that blog is never submitted. /triage accepted
to me this is more about comparing Docker Swarm to Kubernetes. I think it's a good bit of tidying but I'm not sure it's needed for the dockershim removal work.

Discussion:
with your new arguments. {{< note >}} <del> The `command` field corresponds to `entrypoint` in some container runtimes. Refer to the [Notes](#notes) below. </del> <ins> The `command` field corresponds to `entrypoint` in some container runtimes. </ins> {{< /note >}} In this exercise, you create a Pod that runs one container. The configuration

args: ["-c", "while true; do echo hello; sleep 10;done"] ``` <del> ## Notes This table summarizes the field names used by Docker and Kubernetes. |              Description               |    Docker field name   | Kubernetes field name | |----------------------------------------|------------------------|-----------------------| |  The command run by the container      |   Entrypoint           |      command          | |  The arguments passed to the command   |   Cmd                  |      args             | When you override the default Entrypoint and Cmd, these rules apply: * If you do not supply `command` or `args` for a Container, the defaults defined in the Docker image are used. * If you supply a `command` but no `args` for a Container, only the supplied `command` is used. The default EntryPoint and the default Cmd defined in the Docker image are ignored. * If you supply only `args` for a Container, the default Entrypoint defined in the Docker image is run with the `args` that you supplied. * If you supply a `command` and `args`, the default Entrypoint and the default Cmd defined in the Docker image are ignored. Your `command` is run with your `args`. Here are some examples: | Image Entrypoint   |    Image Cmd     | Container command   |  Container args    |    Command run   | |--------------------|------------------|---------------------|--------------------|------------------| |     `[/ep-1]`      |   `[foo bar]`    |   &lt;not set&gt;   |   &lt;not set&gt;  | `[ep-1 foo bar]` | |     `[/ep-1]`      |   `[foo bar]`    |      `[/ep-2]`      |   &lt;not set&gt;  |     `[ep-2]`     | |     `[/ep-1]`      |   `[foo bar]`    |   &lt;not set&gt;   |     `[zoo boo]`    | `[ep-1 zoo boo]` | |     `[/ep-1]`      |   `[foo bar]`    |   `[/ep-2]`         |     `[zoo boo]`    | `[ep-2 zoo boo]` | </del> ## {{% heading "whatsnext" %}} * Learn more about [configuring pods and containers](/docs/tasks/). * Learn more about [running commands in a container](/docs/tasks/debug-application-cluster/get-shell-running-container/). * See [Container](/docs/reference/generated/kubernetes-api/{{< param "version" >}}/#container-v1-core).
Change:
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

Discussion:
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.
Change:
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 I propose that should include Why is this needed The releases page (just the front page, and not requiring any pages within it) is a key document to make available to readers. The shortcode this page uses already has localization support. I think we should localize this page. Comments If we accept this issue, we should also open one issue per downstream localization, about making sure that that localization team works on and localizes for their target localization. Link each of those issues back to this one, which then becomes an umbrella issue.
PS. The localization is on this one, and shows an example of what success looks like. There's one paragraph in the shortcode that doesn't yet localize; if you look at the rendered page you'll see that it's marked as English. Fixing that would be a separate issue.
/triage accepted
/language en /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 : /language en /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
Hi if the issue is still open, can I work on it?
/assign Sure
do you have any questions about how to get started? You're very welcome to open a pull request.
Hey I made the PR, if you can review it that would be great!

Discussion:
Setup | [All heading and subheading URLs](/docs/setup/) Tutorials | [Kubernetes Basics](/docs/tutorials/kubernetes-basics/), [Hello Minikube](/docs/tutorials/hello-minikube/) Site strings | [All site strings](#Site-strings-in-i18n) in a new localized TOML file <ins> Releases | [All heading and subheading URLs](/releases) </ins> Translated documents must reside in their own `content/**/` subdirectory, but otherwise follow the same URL path as the English source. For example, to prepare the [Kubernetes Basics](/docs/tutorials/kubernetes-basics/) tutorial for translation into German, create a subfolder under the `content/de/` folder and copy the English source:
Change:
From : The comment was made in the context of the Dockershim-removal effort. I'm opening this PR following discussions with The warning, which would appear only on posts that are = 1 year old, might read something like this: Comments are welcome. /cc
I'm glad to work on this, though it might not happen until January.
Good idea /area web-development I suggest borrowing the styling from .
/triage accepted
/assign I don't know if the command above will work. If it doesn't or can you assign this to me? I've started working on this now.
Thanks (and the looks to have worked )
/triage duplicate

Discussion:
[options_heading] other = "Options" <ins> [outdated_blog__message] other = "The Kubernetes project considers this article to be outdated because it is more than one year old. Check that the information in the page has not become incorrect since its publication." [outdated_blog__title] other = "Outdated article" </ins> [post_create_issue] other = "Create an issue"

</p> </div> </section> <ins> {{ else if and (eq .Section "blog") .Date (.Date.Before (now.AddDate -1 0 0)) -}} <section id="deprecation-warning" class="outdated-blog"> <div class="content deprecation-warning pageinfo"> <h3>{{ T "outdated_blog__title" }}</h3> <p>{{ T "outdated_blog__message" }}</p> </div> </section> </ins> {{ end }}  No newline at end of file