jiebi/CodeConvo huggingface dataset:
Change:
```powershell stop-service kubelet <del> curl.exe -Lo <kubelet.exe 路径> "https://dl.k8s.io/{{< skew currentPatchVersion >}}/bin/windows/amd64/kubelet.exe" </del> <ins> curl.exe -Lo <kubelet.exe 路径> "https://dl.k8s.io/v{{< skew currentPatchVersion >}}/bin/windows/amd64/kubelet.exe" </ins> restart-service kubelet ```

Discussion:
<!--Required Information--Problem: We've deprecated the param () and now English documents are using instead. (by ) All the other documents need to change into or appropriatly. Since several languages are involved, I'd like to share this issue to check all localizations complete the task. Proposed Solution: For each localization team, search and change appropriately. (See the reference, ) Please check the following task box if the localization task is complete. Page to Update: [x] de [x] es [x] fr [x] hi [x] id [x] ja [x] ko [x] pt-br [x] ru [x] vi [ ] zh-ch [previously done]Once all localizations have switched over, we can remove the parameter from the site.
/assign for the Korean contents.
PR: [ko] Replace deprecated fullversion shortcode for Korean :) The task for Korean can be completed after is merged into the main branch.
/assign For Brazilian Portuguese changes
/triage accepted
/assign For Hindi changes
The Brazilian Portuguese localization has replaced all occurrences via /.
/assign for french content
/reopen
Reopened this issue. <detailsIn response to : /reopen 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
/remove-help
I reopened as there is one more page to fix.
Really done! Thanks folks. /close
Closing this issue. <detailsIn response to : Really done! 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
Change:
- `KubeletPluginsWatcher`: Enable probe-based plugin watcher utility to enable kubelet to discover plugins such as [CSI volume drivers](/docs/concepts/storage/volumes/#csi). - `KubeletPodResources`: Enable the kubelet's pod resources grpc endpoint. <del> See [Support Device Monitoring](https://git.k8s.io/community/keps/sig-node/compute-device-assignment.md) for more details. </del> <ins> See [Support Device Monitoring](https://github.com/kubernetes/enhancements/blob/master/keps/sig-node/compute-device-assignment.md) for more details. </ins> - `LegacyNodeRoleBehavior`: When disabled, legacy behavior in service load balancers and node disruption will ignore the `node-role.kubernetes.io/master` label in favor of the feature-specific labels. - `LocalStorageCapacityIsolation`: Enable the consumption of [local ephemeral storage](/docs/concepts/configuration/manage-compute-resources-container/) and also the `sizeLimit` property of an [emptyDir volume](/docs/concepts/storage/volumes/#emptydir). - `LocalStorageCapacityIsolationFSQuotaMonitoring`: When `LocalStorageCapacityIsolation` is enabled for [local ephemeral storage](/docs/concepts/configuration/manage-compute-resources-container/) and the backing filesystem for [emptyDir volumes](/docs/concepts/storage/volumes/#emptydir) supports project quotas and they are enabled, use project quotas to monitor [emptyDir volume](/docs/concepts/storage/volumes/#emptydir) storage consumption rather than filesystem walk for better performance and accuracy.

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: link At 435 line: See [Support Device Monitoring]() for more details. from link At 479 line: - : Enable service to route traffic based upon the Node topology of the cluster. See [ServiceTopology]() for more details. Proposed Solution: with correct link from link /docs/concepts/services-networking/service-topology/ Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--/language en
/assign
Change:
as terminating (a graceful shutdown duration has been set), the kubelet begins the local Pod shutdown process. 1. If one of the Pod's containers has defined a `preStop` <del> [hook](/docs/concepts/containers/container-lifecycle-hooks/#hook-details), the kubelet </del> <ins> [hook](/docs/concepts/containers/container-lifecycle-hooks), the kubelet </ins> runs that hook inside of the container. If the `preStop` hook is still running after the grace period expires, the kubelet requests a small, one-off grace period extension of 2 seconds.

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: In this page, there is a "hook" link. However, #hook-details doesn't exist in /docs/concepts/containers/container-lifecycle-hooks/. Proposed Solution: The link would be . Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--/language en
/triage accepted /sig node /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 : /triage accepted /sig node /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
Change:
/docs/user-guide/kubectl/     /docs/reference/generated/kubectl/kubectl-options/ /docs/user-guide/kubectl-conventions/     /docs/reference/kubectl/conventions/ /docs/user-guide/kubectl-cheatsheet/     /docs/reference/kubectl/cheatsheet/ <ins> /cheatsheet /docs/reference/kubectl/cheatsheet/ 302 </ins> /docs/user-guide/kubectl/kubectl_*/     /docs/reference/generated/kubectl/kubectl-commands#:splat 301 /docs/user-guide/labels/     /docs/concepts/overview/working-with-objects/labels/ 301 /docs/user-guide/liveness/     /docs/tasks/configure-pod-container/configure-liveness-readiness-startup-probes/ 301

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 Add a short link for the . Why is this needed A short link, eg , is easier to type and remember. Comments I recommend not using the usual 301 redirect here because it's not a permanent move. Instead, use a 307 redirect. Should we repeat this for localizations? Eg In the cheat sheet page itself, consider mentioning the short link in the text of the page. /kind feature /language en
/priority backlog
/assign
Thanks !
Change:
</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

Discussion:
ref: , but this is also just a general feature! Blog posts by their nature go stale over time. This becomes particularly problematic when we decide to deprecate functionality in the project, as those blog posts are forever a part of the docs and forever searchable via Google. Update the blog post's templates (probably , but you may need to copy over from the Docsy theme) to include a warning for blog posts over 1 year old: Some notes: Use standard docsy warning block styles Make sure strings are in localization files so the localization teams know where to look /triage accepted /priority important-soon /area website
The label(s) cannot be applied, because the repository doesn't have them. <detailsIn response to : ref: , but this is also just a general feature! Some notes: Make sure strings are in localization files so the localization teams know where to look /triage accepted /priority important-soon /area website Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details
/assign
/area web-development
Sorry y'all, I hadn't seen this issue before I created . It turns out that there's a clean solution that doesn't involve changes to the blog template. Anyhow, this has been /cc
/close Thanks
Closing this issue. <detailsIn response to : /close 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

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
Change:
apiVersion: v1 kind: Pod metadata: <del> creationTimestamp: "2020-02-12T07:06:16Z" </del> <ins> creationTimestamp: "2024-02-28T22:30:44Z" </ins> generateName: frontend- labels: tier: frontend <del> name: frontend-b2zdv </del> <ins> name: frontend-gbgfx </ins> namespace: default ownerReferences: - apiVersion: apps/v1

Discussion:
Hi Currently we obsrved that following image is not availble
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
can you please provide the page link of the issue?
HI Kubernetes/Website PFA link
/retitle Container image is not available for /kind bug
This looks similar to issue we already have I think it is a duplicate. /triage duplicate
Thanks for raising this! However, closing this request as it closely mirrors the original issue. Feel free to continue the discussion on the original issue. /close not-planned
Closing this issue, marking it as "Not Planned". <detailsIn response to : Thanks for raising this! 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
Change:
Volume | 볼륨 | Waiting | Waiting | 파드의 상태에 한함 Walkthrough | 연습 | <ins> Weave-net | 위브넷(Weave Net) | Weaveworks 사의 솔루션 공식 명칭은 'Weave Net'이므로 한영병기 시 공식 명칭 사용 </ins> Windows | 윈도우 | Worker | 워커 | 노드의 형태에 한함 Workload | 워크로드 |

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 <!-- Describe as precisely as possible how this feature/enhancement should work from the user perspective. What should be changed, etc. --There are several CNI plugins that need to be translated into Korean to be to . English --- --- Calico Cilium Flannel Kube-router Romana Weave-net Weaveworks 'Weave Net' . Why is this needed This is for standardization of terminology when document is localized. Comments <!-- Any additional related comments that might help. Drawings/mockups would be extremely helpful (if required). --Page to update: - /language ko
/assign
Change:
Чтобы загрузить определенную версию, вставьте в фрагмент команды `$(curl -LS https://dl.k8s.io/release/stable.txt)` нужную версию. <del> Например, команда загрузки версии {{< param "fullversion" >}} для macOS будет выглядеть следующим образом: </del> <ins> Например, команда загрузки версии {{< skew currentPatchVersion >}} для macOS будет выглядеть следующим образом: </ins> ``` <del> curl -LO https://dl.k8s.io/release/{{< param "fullversion" >}}/bin/darwin/amd64/kubectl </del> <ins> curl -LO https://dl.k8s.io/release/v{{< skew currentPatchVersion >}}/bin/darwin/amd64/kubectl </ins> ``` 2. Сделайте двоичный файл kubectl исполняемым:

Discussion:
Problem: Based on , I have created this issue/task to help update the [ru] language documentation. Proposed Solution: Page to Update: In the branch, I found: Results for "fullversion" in "k8s-website/content/ru" /home/rdlugyhe/kubernetes/k8s-website/content/ru/docs/tasks/tools/install- 33: Например, для установки версии {{< param "fullversion" }} на Linux введите: 36: {{< param "fullversion" }}/bin/linux/amd64/kubectl 110: Например, для установки версии {{< param "fullversion" }} на macOS введите: 113: {{< param "fullversion" }}/bin/darwin/amd64/kubectl 175: 1. Загрузите последний релиз {{< param "fullversion" }} по этой ссылке. 180: {{< param "fullversion" }} In the branch, I found: Results for "fullversion" in "k8s-website/content/ru" /home/rdlugyhe/kubernetes/k8s-website/content/ru/docs/concepts/containers/container- 44: DNS, если включен . /home/rdlugyhe/kubernetes/k8s-website/content/ru/docs/setup/learning- 222: чтобы запустить Minikube из-под версии {{< param "fullversion" }}, вам нужно выполнить следующую команду: 225: minikube start --kubernetes-version {{< param "fullversion" }} /home/rdlugyhe/kubernetes/k8s-website/content/ru/docs/tasks/tools/install- 36: Например, команда загрузки версии {{< param "fullversion" }} для Linux будет выглядеть следующим образом 39: curl -LO {{< param "fullversion" }}/bin/linux/amd64/kubectl 116: Например, команда загрузки версии {{< param "fullversion" }} для macOS будет выглядеть следующим образом 119: curl -LO {{< param "fullversion" }}/bin/darwin/amd64/kubectl 183: 1.

Загрузите последнюю версию {{< param "fullversion" }} по этой ссылкеe
Change:
{{< note >}} During `kubeadm upgrade`, kubeadm downloads the `KubeletConfiguration` from the <del> `kubelet-config` ConfigMap and overwrite the contents of `/var/lib/kubelet/config.conf`. </del> <ins> `kubelet-config` ConfigMap and overwrite the contents of `/var/lib/kubelet/config.yaml`. </ins> This means that node local configuration must be applied either by flags in `/var/lib/kubelet/kubeadm-flags.env` or by manually updating the contents of <del> `/var/lib/kubelet/config.conf` after `kubeadm upgrade`, and then restarting the kubelet. </del> <ins> `/var/lib/kubelet/config.yaml` after `kubeadm upgrade`, and then restarting the kubelet. </ins> {{< /note >}} ### Applying kube-proxy configuration changes

Discussion:
Run kubeadm upgrade node phase kubelet-config to download the latest kubelet-config ConfigMap contents into the local file The local file name should be
Page related to issue: /language en
/retitle Incorrect file mentioned in command
/sig cluster-lifecycle
plz I want help to fix this /assign
FYI, the same incorrect filename exists in other places on the same page. Two are in the second blue-barred Note pane below the command, and three are further down in the section
(or other maintainers) Can I get confirmation and go ahead please; if this be a tirage-accepted issue to that i can proceed with the fix.
/triage accepted /kind bug Thanks for spotting this.
I have attempt to make fix for this in
Change:
| Python               | [github.com/Frankkkkk/pykorm](https://github.com/Frankkkkk/pykorm) | | Ruby                 | [github.com/abonas/kubeclient](https://github.com/abonas/kubeclient) | | Ruby                 | [github.com/Ch00k/kuber](https://github.com/Ch00k/kuber) | <ins> | Ruby                 | [github.com/k8s-ruby/k8s-ruby](https://github.com/k8s-ruby/k8s-ruby) | </ins> | Ruby                 | [github.com/kontena/k8s-client](https://github.com/kontena/k8s-client) | | Rust                 | [github.com/clux/kube-rs](https://github.com/clux/kube-rs) | | Rust                 | [github.com/ynqa/kubernetes-rust](https://github.com/ynqa/kubernetes-rust) |

Discussion:
They library is mildly defunct now The following project: has been forked and is meant to replace the former per Please update the documentation
Thanks for the suggestion I think we'd be happy to link to an extra project. I'm more wary of removing a project from the list because someone has forked it. If were marked as archived, it'd be easy to agree with the removal. If not, well, maybe we should leave it in and let the reader decide.
OK, with the understanding that we'll add an extra link but won't remove the old one: /triage accepted /language en
/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 : /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
/assign
Change:
`kubeadm kubeconfig user --org system:nodes --client-name system:node:$NODE > kubelet.conf`. `$NODE` must be set to the name of the existing failed node in the cluster. Modify the resulted `kubelet.conf` manually to adjust the cluster name and server endpoint, <del> or pass `kubeconfig user --config` (it accepts `InitConfiguration`). If your cluster does not have </del> <ins> or pass `kubeconfig user --config` (see [Generating kubeconfig files for additional users](/docs/tasks/administer-cluster/kubeadm/kubeadm-certs/#kubeconfig-additional-users)). If your cluster does not have </ins> the `ca.key` you must sign the embedded certificates in the `kubelet.conf` externally. 1. Copy this resulted `kubelet.conf` to `/etc/kubernetes/kubelet.conf` on the failed node. 1. Restart the kubelet (`systemctl restart kubelet`) on the failed node and wait for

Discussion:
In the paragraph under a working control plane node in the cluster that has execute kubeadm kubeconfig user --org system:nodes --client-name system:node:NODE must be set to the name of the existing failed node in the cluster. Modify the resulted manually to adjust the cluster name and server endpoint, or pass kubeconfig user --config (it accepts InitConfiguration). If your cluster does not have the you must sign the embedded certificates in the externally. I do not know where or what the "InitConfiguration" is, nor does the command run without specifying a --config. Could someone add a little more information or example to this?
Page reported in issue: /language en
/retitle Lack of clarity on usage of within the "Troubleshooting kubeadm" page
/sig cluster-lifecycle
all kubeadm commands have reference pages
About InitConfiguration is explained
if you go to that page there is a guide on how to generate kubeconfig files. but the text under should probably mention /help /triage accepted replace: with:
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 : all kubeadm commands have reference pages /triage accepted (it accepts InitConfiguration (see ) </details
/assign
Please review the PR.
I just wanted to say thank you very much. I really appreciate that link going into the paragraph so I can follow it to the reference.
Change:
参阅[容器运行时](/zh-cn/docs/setup/production-environment/container-runtimes/) 以了解更多信息。 <del> <!-- </del> {{< note >}} <ins> <!-- </ins> Docker Engine does not implement the [CRI](/docs/concepts/architecture/cri/) which is a requirement for a container runtime to work with Kubernetes. For that reason, an additional service [cri-dockerd](https://github.com/Mirantis/cri-dockerd) has to be installed. cri-dockerd is a project based on the legacy built-in Docker Engine support that was [removed](/dockershim) from the kubelet in version 1.24. --> <del> {{< note >}} </del> Docker Engine 没有实现 [CRI](/zh-cn/docs/concepts/architecture/cri/)，而这是容器运行时在 Kubernetes 中工作所需要的。 为此，必须安装一个额外的服务 [cri-dockerd](https://github.com/Mirantis/cri-dockerd)。 cri-dockerd 是一个基于传统的内置Docker引擎支持的项目，它在 1.24 版本从 kubelet 中[移除](/zh-cn/dockershim)。

Discussion:
(kubeadm) []
/triage accepted /kind bug /assign /language zh
Change:
</a> <ul> {% for version in page.versions %} <del> <li><a href="{{ version.url }}">{{ version.version }}</a></li> </del> <ins> {% if page.versionedurl contains version.version %} <li><a href="{{ version.url }}{{ page.versionedurl[version.version] }}">{{ version.version }}</a></li> {% else  %} <li><a href="{{ version.url }}{{ page.url }}">{{ version.version }}</a></li> {% endif %} </ins> {% endfor %} </ul> </li>

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] --- [x] Feature Request [ ] Bug Report Problem: When switching to a different version of the docs, I get redirected to the root of the doc tree. Proposed Solution: Would be nice to redirect users to an equivalent page in the previous version of docs. Easy way to get started would be to just support pages that haven't moved or been refactored. Could get fancier after that.
Also related (found while I was reproducing this), the drop-down mechanism that allows version changing doesn't render correctly on safari (mobile or laptop) so that you can't choose the older versions, and the same happens in Chrome (IOS) - you see part of 1.8, but the rest of the list is cut off. See embedded screenshot (from Chrome IOS) !
I've attempted to implement a solution to this in . This part works by default This part requires setting data on the page as to where to send the person.
This issue is still present on the current version of the website.
not sure if we should reopen this issue or file a new one as a bug report but this no longer works. from what I can tell during the migration to hugo the header file was removed