jiebi/CodeConvo huggingface dataset:
Change:
`port-forward`    | `kubectl port-forward POD [LOCAL_PORT:]REMOTE_PORT [...[LOCAL_PORT_N:]REMOTE_PORT_N] [flags]` | Forward one or more local ports to a pod. `proxy`        | `kubectl proxy [--port=PORT] [--www=static-dir] [--www-prefix=prefix] [--api-prefix=prefix] [flags]` | Run a proxy to the Kubernetes API server. `replace`        | `kubectl replace -f FILENAME` | Replace a resource from a file or stdin. <del> `run`        | </code>kubectl run NAME --image=image [--env="key=value"] [--port=port] [--replicas=replicas] [--dry-run=server&#124;client&#124;none] [--overrides=inline-json] [flags]</code> | Run a specified image on the cluster. </del> <ins> `run`        | <code>kubectl run NAME --image=image [--env="key=value"] [--port=port] [--dry-run=server&#124;client&#124;none] [--overrides=inline-json] [flags]</code> | Run a specified image on the cluster. </ins> `scale`        | <code>kubectl scale (-f FILENAME &#124; TYPE NAME &#124; TYPE/NAME) --replicas=COUNT [--resource-version=version] [--current-replicas=count] [flags]</code> | Update the size of the specified replication controller. `version`        | `kubectl version [--client] [flags]` | Display the Kubernetes version running on the client and server.

Discussion:
This is a Bug Report Problem: The reference documentation for kubectl v1.18 does not match the implementation regarding command and its options and . Proposed Solution: Update the reference docs. Pages to Update: , the sections for options replicas and restart are incorrect. The option is depreciated and always creates a pod regardless of the , the following line: The option is depreciated.
/assign
Thanks for contributing
Change:
defaultValue: false fromVersion: "1.29" --- <del> Enables images to be pulled based on the [runtime class] (/docs/concepts/containers/runtime-class/) of the pods that reference them. </del> <ins> Enables images to be pulled based on the [runtime class](/docs/concepts/containers/runtime-class/) of the pods that reference them. </ins>

Discussion:
This is a Bug Report Problem: In the of the page, there is a section of that has an issue with the hyperlinking of the text. The is not hyperlinked properly. Proposed Solution: We should link the with the appropriate link, i.e., Page to Update:
/language en
I would to like to work on this issue, if the triage gets accepted.
/retitle Broken link in the description of on "Feature Gates" page
Fixes are welcomed. /triage accepted /priority backlog
I have raised PR to fix this problem.
Could you please review and merge the PR whenever free.
Change:
### Instalar el binario de kubectl con curl en Windows <del> 1. Descarga la [última versión {{< param "fullversion" >}}](https://dl.k8s.io/release/{{< param "fullversion" >}}/bin/windows/amd64/kubectl.exe). </del> <ins> 1. Descarga la [última versión {{< skew currentPatchVersion >}}](https://dl.k8s.io/release/v{{< skew currentPatchVersion >}}/bin/windows/amd64/kubectl.exe). </ins> O si tiene `curl` instalado, use este comando: ```powershell <del> curl -LO https://dl.k8s.io/release/{{% param "fullversion" %}}/bin/windows/amd64/kubectl.exe </del> <ins> curl -LO https://dl.k8s.io/release/v{{% skew currentPatchVersion %}}/bin/windows/amd64/kubectl.exe </ins> ``` {{< note >}}

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 param is deprecated. Proposed Solution: Replace the shortcode (Spanish pages), for example with or something close. <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--Part of /language es
/triage accepted /area localization /priority backlog
Change:
### Hook handler implementations Containers can access a hook by implementing and registering a handler for that hook. <del> There are two types of hook handlers that can be implemented for Containers: </del> <ins> There are three types of hook handlers that can be implemented for Containers: </ins> * Exec - Executes a specific command, such as `pre-stop.sh`, inside the cgroups and namespaces of the Container. Resources consumed by the command are counted against the Container.

Discussion:
This is a Bug Report Fix number of types of hook handlers available to implement for Containers Problem: In the section , it's referred as just 2 possible types of hook handlers for containers , but afterwards 3 are enumerated Proposed Solution: "There are three types of hook handlers that can be implemented for Containers:" Page to Update:
/language en
I will try to help with this! /assign
/triage accepted
Change:
layout: blog title:  '在 Kubernetes 上对 gRPC 服务器进行健康检查' date: 2018-10-01 <ins> slug: health-checking-grpc-servers-on-kubernetes </ins> --- <!-- <del> --- </del> layout: blog title:  'Health checking gRPC servers on Kubernetes' date: 2018-10-01 <del> --- </del> ---> <!--

Discussion:
This is a Feature Request This page blog/2022/05/13/grpc-probes-in- has no Chinese version What would you like to be Translate Chinese version for blog/2022/05/13/grpc-probes-in- Comments /language zh /assign
/triage accepted
Change:
At this point, we believe that there is feature parity between Docker and the other runtimes. Many end-users have used our [migration guide](/docs/tasks/administer-cluster/migrating-from-dockershim/) and are running production workload using these different runtimes. The plan of <del> record today is that dockershim will be removed in version 1.24, slated for </del> <ins> record today is that dockershim will be removed in version 1.24, slated for </ins> release around April of next year. For those developing or running alpha and beta versions, dockershim will be removed in December at the beginning of the 1.24 release development cycle.

Discussion:
Pre the first alpha cut of 1.24, a blog post should be drafted expressing the project's understanding that many users have not migrated off of dockershim, and migration can be painful but its needed for a variety of reasons and we are committed to documenting and making it as easy as possible. /assign (For visibility) /assign sig-arch / sig-node (please loop in / assign others) /assign (for myself to keep track of) /sig node architecture /priority important-soon /area blog
:100: /triage accepted
hoping can cover for me! also cc
/assign
I started the draft, which is super rough and doesnt' have all the outline yet:
IMO the draft is in a good enough place to be converted to a PR.
Change:
<!-- maintenance note: OK to remove all mention of glusterfs once the v1.25 release of Kubernetes has gone out of support --> <del> - </del> Kubernetes {{< skew currentVersion >}} does not include a `glusterfs` volume type. The GlusterFS in-tree storage driver was deprecated in the Kubernetes v1.25 release

Discussion:
This is a Bug Report Problem: Under concept page, content for volume type is missing. In it is mentioned like: ! Due to this, content() is missing from the page: ! Instead of that it should be like the below screenshot: ! Proposed Solution: Above missing content Content for should be there. Page to Update:
/assign
/sig docs
Fixed it here:
/triage accepted /retitle Formatting problem for volume details in Volumes concept /language en
Change:
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`

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: 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
Change:
### Upgrade kubeadm <del> 1.  Upgrade kubeadm on all worker nodes: </del> <ins> -  Upgrade kubeadm on all worker nodes: </ins> <del> {{< tabs name="k8s_install_kubeadm_worker_nodes" >}} {{% tab name="Ubuntu, Debian or HypriotOS" %}} </del> <ins> {{< tabs name="k8s_install_kubeadm_worker_nodes" >}} {{% tab name="Ubuntu, Debian or HypriotOS" %}} </ins> # replace x in 1.18.x-00 with the latest patch version apt-mark unhold kubeadm &&  apt-get update && apt-get install -y kubeadm=1.18.x-00 &&  apt-mark hold kubeadm <ins> - </ins> # since apt-get version 1.1 you can also use the following method apt-get update &&  apt-get install -y --allow-change-held-packages kubeadm=1.18.x-00 <del> {{% /tab %}} {{% tab name="CentOS, RHEL or Fedora" %}} </del> <ins> {{% /tab %}} {{% tab name="CentOS, RHEL or Fedora" %}} </ins> # replace x in 1.18.x-0 with the latest patch version yum install -y kubeadm-1.18.x-0 --disableexcludes=kubernetes <del> {{% /tab %}} {{< /tabs >}} </del> <ins> {{% /tab %}} {{< /tabs >}} </ins> ### Drain the node <del> 1.  Prepare the node for maintenance by marking it unschedulable and evicting the workloads: </del> <ins> -  Prepare the node for maintenance by marking it unschedulable and evicting the workloads: </ins> ```shell # replace <node-to-drain> with the name of your node you are draining

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--indentation issue Proposed Solution: Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--18 <!--Additional Information:--fix the page indentation
/sig cluster-lifecycle docs hi, can you show which section you think is wrong or maybe provide a screenshot?
/sig cluster-lifecycle docs Attached screenshots
i don't see the attachments, possibly because you replied via email. try adding them using the GitHub web UI.
! ! ! !
Page alignment or indentation not proper looks.
ok, i can confirm this. hi, was this broken by this PR, or maybe something on the hugo side changed recently?
The Hugo upgrade was PR
/kind bug /priority important-longterm
I've tried to make a work around for this. It looks like tabs shortcodes with code snippets inside them don't play well with shortcodes (see issue ).
I will take a stab at cleaning this up assuming work isn't currently being done. We might have to adjust the page slightly until capture is removed. /assign
I can share some WIP in case it helps
thanks for taking a look and
oof, sorry I saw this after I opened the PR. That does help! I was scratching my head on some of these bugs. Let me know if you want me to modify my PR to incorporate some of your suggestions or vice versa. I was poking fun of the page on twitter and felt obligated to try to fix it :smile:
Busy at the moment I'm afraid. Feel free to snarf any bits that look useful.
Change:
docs/user-guide/logging/#cluster-level-logging-to-google-cloud-logging) * [Cluster-level Logging with Elasticsearch and Kibana]( <del> docs/user-guide/logging/#cluster-level-logging-with-elasticsearch-and-kibana) </del> <ins> docs/getting-started-guides/logging-elasticsearch/) </ins> ## Node components

Discussion:
I wish /docs/admin/cluster-components/ Didn't have a broken link to Cluster Logging with ELK
Change:
<del> <!-- </del> <ins> --- </ins> api_metadata: apiVersion: "" import: "k8s.io/apimachinery/pkg/apis/meta/v1" kind: "LabelSelector" content_type: "api_reference" <del> description: "A label selector is a label query over a set of resources." title: "LabelSelector" </del> <ins> description: "标签选择器是对一组资源的标签查询。" title: "标签选择器" </ins> weight: 2 <del> --> </del> <ins> auto_generated: true </ins> --- <ins> <!-- </ins> api_metadata: apiVersion: "" import: "k8s.io/apimachinery/pkg/apis/meta/v1" kind: "LabelSelector" content_type: "api_reference" <del> description: "标签选择器是对一组资源的标签查询。" title: "标签选择器" </del> <ins> description: "A label selector is a label query over a set of resources." title: "LabelSelector" </ins> weight: 2 <del> auto_generated: true --- </del> <ins> --> </ins> `import "k8s.io/apimachinery/pkg/apis/meta/v1"`

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: Wrong rendering in ! cf. en version page: ! en file: zh file: Proposed Solution: Place Hugo-related fields in the beginning of . Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--/language zh /assign
This issue is currently awaiting triage. SIG Docs takes a lead on issue triage for this website, but any Kubernetes member can accept issues by applying the label. The label can be by org members by writing in a comment. <detailsInstructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details
Change:
This annotation has been deprecated. <ins> ### volume.beta.kubernetes.io/mount-options (deprecated) {#mount-options} Example : `volume.beta.kubernetes.io/mount-options: "ro,soft"` Used on: PersistentVolume A Kubernetes administrator can specify additional [mount options](/docs/concepts/storage/persistent-volumes/#mount-options) for when a PersistentVolume is mounted on a node. This annotation has been deprecated. </ins> ### volume.kubernetes.io/storage-provisioner Used on: PersistentVolumeClaim

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 volume mount mechanism in Kubernetes used to rely on an unregistered annotation. That annotation () is already document, but isn't yet registered. Proposed Solution: Add to (list it as deprecated) Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--Additional Information: /language en /kind bug /priority backlog
You can refer to for details of what the annotation does. Also the text of the annotation description should in any case hyperlink to so that readers can learn about the mechanism that replaced it.
/sig storage I would like to give a try.
/sig storage /assign
/triage accepted
Change:
fromVersion: "1.23" toVersion: "1.26" - stage: beta <del> defaultValue: false </del> <ins> defaultValue: true </ins> fromVersion: "1.27" --- Allows the use of the optional `.spec.persistentVolumeClaimRetentionPolicy` field,

Discussion:
This is a Bug Report default value for StatefulsetAutoDeletePVC is true in 1.27 <!-- 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: Proposed Solution: Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--
/language en
page to update
/assign
/triage accepted /sig apps
Change:
title: Picking the Right Solution --- <del> Kubernetes can run on various platforms: from your laptop, to VMs on a cloud provider, to rack of </del> <ins> Kubernetes can run on various platforms: from your laptop, to VMs on a cloud provider, to a rack of </ins> bare metal servers. The effort required to set up a cluster varies from running a single command to crafting your own customized cluster. Use this guide to choose a solution that fits your needs.

Discussion:
<!-- Thanks for filing an issue! Before submitting, please fill in the following information. --<!--Required Information--This is a... [ ] Feature Request [x] Bug Report Problem: For users using K8S versions 1.8 and lower that don't have the fix contained in it may be necessary to set for the OpenStack cloud provider when installing on OpenStack clusters that expose their Cinder endpoint using paths rather than ports to avoid auto-detection errors such as: This includes for users trying out K8S on a devstack environment, and potentially other deployment tools. In this situation it is possible to resolve using: Valid values for are: With being the default. Proposed Solution: Highlight the bs-version parameter as optional (so not minimal configuration) but required in some circumstances. Page to Update:
Change:
- tallclair title: Pod Overhead content_template: templates/concept <del> weight: 20 </del> <ins> weight: 50 </ins> --- {{% capture overview %}}

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 write a new concept page: (or possibly ) If the does not work as the page overview, consider tweaking the glossary entry so that it does. Then use a Hugo shortcode. Why is this needed ConfigMap is a core object type for Kubernetes; as such, it needs documenting properly. Comments Consider using as an example for page structure. It's better to put Task-style documentation in task pages such as and then hyperlink to those from the Concept page. Also see: /docs/user-guide/configmap need more details on ConfigMap updates Actionable user-guide/configmap does not document self-updating It's unclear what happens when ConfigMap is changed Need doc on using ConfigMap updates Wanted: ConfigMap Rollout Options Doc
/language en /sig apps
/priority important-longterm
This is worth prioritizing /priority important-soon
/remove-priority important-longterm
/project Doc Sprints
/assign
/unassign
Issues go stale after 90d of inactivity. Mark the issue as fresh with . Stale issues rot after an additional 30d of inactivity and eventually close. If this issue is safe to close now please do so with . Send feedback to sig-testing, kubernetes/test-infra and/or . /lifecycle stale
Still worth documenting /remove-lifecycle stale
/reopen let's collaborate on this!
Change:
{{/* We cache this partial for bigger sites and set the active class client side. */}} <del> {{ $sidebarCacheLimit := cond (isset .Site.Params.ui "sidebar_cache_limit") .Site.Params.ui.sidebar_cache_limit 2000 }} {{ $shouldDelayActive := ge (len .Site.Pages) $sidebarCacheLimit }} </del> <ins> {{ $sidebarCacheLimit := cond (isset .Site.Params.ui "sidebar_cache_limit") .Site.Params.ui.sidebar_cache_limit 2000 -}} {{ $shouldDelayActive := ge (len .Site.Pages) $sidebarCacheLimit -}} </ins> <div id="td-sidebar-menu" class="td-sidebar__inner{{ if $shouldDelayActive }} d-none{{ end }}"> <del> {{ if not .Site.Params.ui.sidebar_search_disable }} </del> <ins> {{ if not .Site.Params.ui.sidebar_search_disable -}} </ins> <form class="td-sidebar__search d-flex align-items-center"> {{ partial "search-input.html" . }} <button class="btn btn-link td-sidebar__toggle d-md-none p-0 ml-3 fas fa-bars" type="button" data-toggle="collapse" data-target="#td-section-nav" aria-controls="td-docs-nav" aria-expanded="false" aria-label="Toggle section navigation"> </button> </form> <del> {{ else }} </del> <ins> {{ else -}} </ins> <div id="content-mobile"> <form class="td-sidebar__search d-flex align-items-center"> {{ partial "search-input.html" . }}

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: I saw by accident very big page files on Kubernetes documentation. For example is lines long and the lines 286- are taken for the sidebar menu containing a lot of whitespace (do right-mouse and "view page source"). Proposed Solution: I reported the issue already with Docsy: and proposed a pull request. But this will not be enough. Somebody has to update too. 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
/assign
The hugo Docsy theme side issue is resolved and closed: When will somebody review and implement pull request ? You can do this separate from a Docsy theme update at It is only about (huge) whitespace reduction, not a functional change. But k8s website users will benefit in user experience.
Change:
StatefulSetのPodについては、[StatefulSetからPodを削除するためのタスクのドキュメント](/ja/docs/tasks/run-application/force-delete-stateful-set-pod/)を参照してください。 <del> ### 失敗したPodのガベージコレクション {#pod-garbage-collection} </del> <ins> ### 終了したPodのガベージコレクション {#pod-garbage-collection} </ins> 失敗したPodは人間または{{< glossary_tooltip term_id="controller" text="controller" >}}が明示的に削除するまで存在します。

Discussion:
This is a Feature Request What would you like to be We need to update content/ja/docs/concepts/architecture/garbage- according to the English text, because it is outdated. Why is this needed content/ja/docs/concepts/architecture/garbage- is outdated. A link text to this page from other pages have already been fixed. The current page is still "" and it should be fixed "". Comments /language ja /assign
This issue is currently awaiting triage. SIG Docs takes a lead on issue triage for this website, but any Kubernetes member can accept issues by applying the label. The label can be by org members by writing in a comment. <detailsInstructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details
Change:
--> 如果你希望新来的 Pod 均匀分布在现有的可用区域，则可以按如下设置其清单： <del> {{< codenew file="pods/topology-spread-constraints/one-constraint.yaml" >}} </del> <ins> {{% code file="pods/topology-spread-constraints/one-constraint.yaml" %}} </ins> <!-- From that manifest, `topologyKey: zone` implies the even distribution will only be applied

Discussion:
the Chinese translation is wrong, "" should be "" see from English site:
/language zh
The label(s) cannot be applied, because the repository doesn't have them. <detailsIn response to : /language zh-cn </details
/language zh
/sig docs
/triage accepted
/assign