jiebi/CodeConvo huggingface dataset:
Change:
<h2>Get Kubernetes Certified</h2> <div class="col-container"> <div class="col-nav"> <ins> <h5> <b>Kubernetes and Cloud Native Associate (KCNA)</b> </h5> <p>The Kubernetes and Cloud Native Associate (KCNA) exam demonstrates a user’s foundational knowledge and skills in Kubernetes and the wider cloud native ecosystem.</p> <p>A certified KCNA will confirm conceptual knowledge of the entire cloud native ecosystem, particularly focusing on Kubernetes.</p> <br> <a href="https://training.linuxfoundation.org/certification/kubernetes-cloud-native-associate/" target="_blank" class="button">Go to Certification</a> </div> <div class="col-nav"> </ins> <h5> <b>Certified Kubernetes Application Developer (CKAD)</b> </h5>

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 to mention the qualification. Why is this needed There's now a KCNA qualification that you can train for. Comments /kind feature /language en /priority important-longterm
/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 : /help /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
/assign (I just modified the in the training folder, please LMK if that was not the right way)
That's how we do it. As a separate issue: it'd be nice to convert that to a kind of HTML that's closer to what Docsy renders our site to.
Change:
### Additional information <del> - [Draining nodes](/docs/tasks/administer-cluster/safely-drain-node/) before kubelet MINOR version upgrades is required. In the case of control plane nodes, they could be running CoreDNS Pods or other critical workloads. </del> <ins> - The instructions below outline when to drain each node during the upgrade process. If you are performing a **minor** version upgrade for any kubelet, you **must** first drain the node (or nodes) that you are upgrading. In the case of control plane nodes, they could be running CoreDNS Pods or other critical workloads. For more information see [Draining nodes](/docs/tasks/administer-cluster/safely-drain-node/). </ins> - All containers are restarted after upgrade, because the container spec hash value is changed. <!-- steps -->

Discussion:
this documentation is so confusing.... Why section for Draining a node is in the middle when we talk about it at the begining? How one would drain first master node? After 'sudo kubeadm upgrade apply'?
/language en /sig cluster-lifecycle
this is the second report i've seen about this so maybe we can improve the structure a little but i need to understand how.. by "beginning" do you mean ? this simply explains why draining nodes is required. if you look at the structure on the right you will see that "calling kubeadm upgrade" is meant for all control plane nodes, since it's under the parent "Upgrading control plane nodes". this means you have to go to all of them and first call "upgrade apply" or "upgrade node". then "Draining the node" is a separate section also means - do it for all control plane nodes. ! Also under "Upgrading control plane nodes" there is this text: as a user, what would you like to see as an improvement here? /triage accepted /priority awaiting-more-evidence
The upgrade procedure on control plane nodes should be executed one node at a time perhaps this text can be adjusted to the following:
Hi, 'Additional information' section at the beginning confirms that 'Draining nodes' is the very first thing to do: but that is not the case 'draining a node is a necessary step before upgrading a kubelet on a node for all node types': This is an important point and to be mentioned in the document else assumption is to drain the node before initiating upgrade action. Regards, Rajive
ok, i can see how that can be confusing. the text has a link and it sounds like a prerequisite. this can be clarified that the steps below instruct exactly when to do the drain during upgrade.
/assign /remove-priority important-more-evidence /priority backlog
Those labels are not set on the issue: <detailsIn response to : /assign /remove-priority important-more-evidence /priority backlog 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-priority awaiting-more-evidence
proposed fix is here:
Hi... This is awesome. Thank you very much..
Change:
details. {{< /caution >}} <ins> ### service.beta.kubernetes.io/azure-load-balancer-disable-tcp-reset (deprecated) {#service-beta-kubernetes-azure-load-balancer-disble-tcp-reset} Example: `service.beta.kubernetes.io/azure-load-balancer-disable-tcp-reset: "false"` Used on: Service This annotation only works for Azure standard load balancer backed service. This annotation is used on the Service to specify whether the load balancer should disable or enable TCP reset on idle timeout. If enabled, it helps applications to behave more predictably, to detect the termination of a connection, remove expired connections and initiate new connections. You can set the value to be either true or false. See [Load Balancer TCP Reset](https://learn.microsoft.com/en-gb/azure/load-balancer/load-balancer-tcp-reset) for more information. {{< note >}} This annotation is deprecated. {{< /note >}} </ins> ### pod-security.kubernetes.io/enforce Type: Label

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 Document (and register) the legacy annotation The page to change is: Why is this needed We try to document all of our annotations, even the ones we ask people to stop using. Comments /language en /lifecycle frozen /sig network cloud-provider
Could be useful, let's consider doing this. /triage accepted /priority backlog
I'd like to work on it /assign I'll share the findings here so the content is confirmed first.
How's this :
I got reference from cloud-provider-azure and Microsoft docs.
From it looks like we need a pile of other issues about unregistered annotations for this cloud provider.
Yes, you can find the other annotations here: https://cloud-provider-
Change:
- [聚合器（Aggregator）](https://github.com/kubernetes/community/blob/master/contributors/design-proposals/api-machinery/aggregated-api-servers.md)具有完整的 Kubernetes API 语义，用以实现用户自己的 apiserver。 <!-- <del> ## Enabling API groups </del> <ins> ## Enabling or disabling API groups </ins> Certain resources and API groups are enabled by default. You can enable or disable them by setting `--runtime-config` on the apiserver. `--runtime-config` accepts comma separated values. For example:

Discussion:
This is a Feature Request Since v1.16, extensions/v1beta1 has been deleted and it should not be used in docs What would you like to be The following pages should be edited due to this deletion. [ ] [ ] [x] [ ] [ ] [ ] [ ] [ ] [x] [x] Why is this needed extensions/v1beta1 is deleted in 1.16 Comments
/kind cleanup /priority important-soon (I think)
If you are looking at this as potentially something to contribute to, it's OK to suggest a PR that fixes only one page, or only some pages. If you do that please mention “Partial fix for issue ” in the description of your PR.
thanks for contribution here. Could you please share which pages would you take? Let us make the assignment more clear and help other contributors easily start their work.
Thank you for your comments. I wrote the target file into PR titles. And I will write to the comment about netlify demo pages and original pages to enable checking the diff easily.
Change:
## {{% heading "whatsnext" %}} <del> `VerticalPodAutoscaler` is a custom resource that you can deploy into your cluster </del> <ins> * `VerticalPodAutoscaler` is a custom resource that you can deploy into your cluster </ins> to help you manage resource requests and limits for pods. <del> Visit [Vertical Pod Autoscaler](https://github.com/kubernetes/autoscaler/tree/master/vertical-pod-autoscaler#readme) to learn more about `VerticalPodAutoscaler` and how you can use it to scale cluster </del> <ins> Learn more about [Vertical Pod Autoscaler](https://github.com/kubernetes/autoscaler/tree/master/vertical-pod-autoscaler#readme) and how you can use it to scale cluster </ins> components, including cluster-critical addons. <del> The [cluster autoscaler](https://github.com/kubernetes/autoscaler/tree/master/cluster-autoscaler#readme) </del> <ins> * The [cluster autoscaler](https://github.com/kubernetes/autoscaler/tree/master/cluster-autoscaler#readme) </ins> integrates with a number of cloud providers to help you run the right number of nodes for the level of resource demand in your cluster. <del> The [addon resizer](https://github.com/kubernetes/autoscaler/tree/master/addon-resizer#readme) helps you in resizing the addons automatically as your cluster's scale changes. </del>  No newline at end of file <ins> * The [addon resizer](https://github.com/kubernetes/autoscaler/tree/master/addon-resizer#readme) helps you in resizing the addons automatically as your cluster's scale changes. </ins>

Discussion:
This is a Bug Report Problem: section in file should have the points in Bullet format ( • ) to sync with other page formates. Proposed Solution: Change the format of text under section in file to Bullet format. Page to Update:
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 /assign
If traige is accepted, i would be happy to contribute on it.
Fixed it here .
Change:
<ins> --- title: "管理 Secrets" weight: 28 description: 使用 Secrets 管理机密配置数据. --- </ins>  No newline at end of file

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: is missing in Chinese version. See for more info. Proposed Solution: Add /docs/tasks/configmap-secret/ to zh version with three articles to be translated. [x] /zh/docs/tasks/configmap-secret/managing-secret-using-config-[x] /zh/docs/tasks/configmap-secret/managing-secret-using-[x] /zh/docs/tasks/configmap-secret/managing-secret-using- Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--
/language zh /assign
Change:
gpgcheck=1 gpgkey=https://pkgs.k8s.io/core:/stable:/{{< param "version" >}}/rpm/repodata/repomd.xml.key EOF <ins> ``` </ins> <del> {{< note >}} To upgrade kubectl to another minor release, you'll need to bump the version in `/etc/zypp/repos.d/kubernetes.repo` before running `zypper update`. This procedure is described in more detail in [Changing The Kubernetes Package Repository](/docs/tasks/administer-cluster/kubeadm/change-package-repository/). {{< /note >}} </del> <ins> {{< note >}} To upgrade kubectl to another minor release, you'll need to bump the version in `/etc/zypp/repos.d/kubernetes.repo` before running `zypper update`. This procedure is described in more detail in [Changing The Kubernetes Package Repository](/docs/tasks/administer-cluster/kubeadm/change-package-repository/). {{< /note >}} </ins> <del> 1. Install kubectl using `zypper`: </del> <ins> 2. Install kubectl using `zypper`: </ins> <del> ```bash sudo zypper install -y kubectl </del> <ins> ```bash sudo zypper install -y kubectl ``` </ins> {{% /tab %}} {{< /tabs >}}

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: [Install and Set Up kubectl on Linux] page layout is collapsed. Right side layout is displaced to down. Proposed Solution: Right side layout should be in place. Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--Additional Information: !
/language en /area web-development
I will try to help with this. /assign
(or any maintainers) Can i get some hint and go ahead to work on this please?
It appears that the changes in have inadvertently resulted in the layout of page broken. Potentially addressing could solve it.
We should fix the layout of the page. /triage accepted /priority backlog
/retitle Page layout for "Install and Set Up kubectl on Linux" is broken
/remove-area web-development This is more of a content fix.
Change:
`1.12`, you should set hidden metrics via command line: `--show-hidden-metrics=1.12` and remember to remove this metric dependency before upgrading to `1.14` <del> ## Disable accelerator metrics The kubelet collects accelerator metrics through cAdvisor. To collect these metrics, for accelerators like NVIDIA GPUs, kubelet held an open handle on the driver. This meant that in order to perform infrastructure changes (for example, updating the driver), a cluster administrator needed to stop the kubelet agent. The responsibility for collecting accelerator metrics now belongs to the vendor rather than the kubelet. Vendors must provide a container that collects metrics and exposes them to the metrics service (for example, Prometheus). The [`DisableAcceleratorUsageMetrics` feature gate](/docs/reference/command-line-tools-reference/feature-gates/) disables metrics collected by the kubelet, with a [timeline for enabling this feature by default](https://github.com/kubernetes/enhancements/tree/411e51027db842355bd489691af897afc1a41a5e/keps/sig-node/1867-disable-accelerator-usage-metrics#graduation-criteria). </del> ## Component metrics ### kube-controller-manager metrics

Discussion:
According to the "DisableAcceleratorUsageMetrics" feature gate has already been removed, so the section "Disable accelerator metrics" needs to be updated.
/sig node instrumentation /language en /kind bug /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 : /sig node instrumentation /language en /kind bug /help /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
/assign
Change:
## セットアップ <del> RuntimeClass機能のフィーチャーゲートが有効になっていることを確認してください(デフォルトで有効です)。フィーチャーゲートを有効にする方法については、[フィーチャーゲート](/ja/docs/reference/command-line-tools-reference/feature-gates/)を参照してください。 その`RuntimeClass`のフィーチャーゲートはApiServerとkubeletのどちらも有効になっていなければなりません。 </del> 1. ノード上でCRI実装を設定する。(ランタイムに依存) 2. 対応するRuntimeClassリソースを作成する。

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:
`status.podIP` : the pod's primary IP address (usually, its IPv4 address) <del> In addition, the following information is available through a `downwardAPI` volume `fieldRef`, but **not as environment variables**: </del> <ins> The following information is available through a `downwardAPI` volume `fieldRef`, **but not as environment variables**: </ins> `metadata.labels` : all of the pod's labels, formatted as `label-key="escaped-label-value"` with one label per line

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: Documentation should state that spec and status downward API fields are only available as environment variables, not as files. Proposed Solution: Add text before spec.serviceAccountName stating: Then for consistency, a few lines down change: to Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--Kubernetes Version: Confirmed on v1.24 and v1.25 Additional Information: Error message from kubectl (1.25) apply shows which values are allowed for each type (line breaks for readability)
Thanks for the report /sig node
/triage accepted sounds reasonable, thank you
I would like to give a try on this. /assign
Change:
<!-- ## Services <ins> * [Connecting Applications with Services](/docs/tutorials/services/connect-applications-service/) </ins> * [Using Source IP](/docs/tutorials/services/source-ip/) --> ## 服务  {#services} <ins> * [使用 Service 连接到应用](/zh-cn/docs/tutorials/services/connect-applications-service/) </ins> * [使用源 IP](/zh-cn/docs/tutorials/services/source-ip/) <!--

Discussion:
Numbers in the following list may be not up to date. Please run again before working on each of them.
/language zh /triage accepted /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 zh /triage accepted /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:
<ins> apiVersion: v1 kind: Service metadata: name: my-service spec: ipFamily: IPv4 selector: app: MyApp ports: - protocol: TCP port: 80 targetPort: 9376 </ins>  No newline at end of file

Discussion:
This is a Feature Request What would you like to be Translate into Japanese. Why is this needed This page has not been translated. Comments /language ja /assign
Change:
title: 容器运行环境（Container Runtime） id: container-runtime date: 2019-06-05 <del> full_link: /docs/reference/generated/container-runtime </del> <ins> full_link: /docs/setup/production-environment/container-runtimes </ins> short_description: > 容器运行环境是负责运行容器的软件。

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: Clicking the "" hyperlink leads to the 404 page. <img width="876" alt="WeChatc2b6a16c89afc8d1086c8c92a0a7f437" src="https://user-"Proposed Solution: correct link as below: full_link: /docs/setup/production-environment/container-runtimes <!--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
/language zh
Change:
The second element specifies that the value of the Pod's `annotations` field should be stored in a file named `annotations`. --> <del> 在配置文件中，你可以看到 Pod 有一个 `downwardAPI` 类型的卷，并且挂载到容器中的 `/etc` 目录。 </del> <ins> 在配置文件中，你可以看到 Pod 有一个 `downwardAPI` 类型的卷，并且挂载到容器中的 `/etc/podinfo` 目录。 </ins> 查看 `downwardAPI` 下面的 `items` 数组。 每个数组元素都是一个

Discussion:
the file labels and annotations should be in the directory /etc/podinfo not /etc !
Hi What's the URL of the web page that isn't right? /triage needs-information
/triage accepted
/assign
Change:
<button id="desktopShowVideoButton" onclick="kub.showVideo()">Watch Video</button> <br> <br> <del> <a href="https://events.linuxfoundation.org/kubecon-cloudnativecon-europe/" button id="desktopKCButton">Attend KubeCon + CloudNativeCon Europe on March 19-22, 2024</a> </del> <ins> <a href="https://events.linuxfoundation.org/kubecon-cloudnativecon-open-source-summit-ai-dev-china/" button id="desktopKCButton">Attend KubeCon + CloudNativeCon China on August 21-23</a> </ins> <br> <br> <br> <ins> <a href="https://events.linuxfoundation.org/kubecon-cloudnativecon-north-america-2024/" button id="desktopKCButton">Attend KubeCon + CloudNativeCon North America on November 12-15</a> </ins> <br> <del> <a href="https://events.linuxfoundation.org/kubecon-cloudnativecon-north-america-2024/" button id="desktopKCButton">Attend KubeCon + CloudNativeCon North America on November 12-15, 2024</a> </del> <ins> <br> <br> <a href="https://events.linuxfoundation.org/kubecon-cloudnativecon-india/" button id="desktopKCButton">Attend KubeCon + CloudNativeCon India on December 11-12</a> </ins> </div> <div id="videoPlayer"> <iframe data-url="https://www.youtube.com/embed/H06qrNmGqyE?autoplay=1" frameborder="0" allowfullscreen></iframe>

Discussion:
This is a Bug Report Problem: The main page currently offers to visit KubeCon Europe 2024 (which has passed already) and KubeCon NA 2024 (which is valid). AFAIR, this page has always listed two upcoming KubeCon events in Europe + NA. However: doesn't seem to be an official date for the next KubeCon Europe yet. seems reasonable to promote other locations as well. According to the , the next KubeCon will happen in Hong Kong (21-23 August, 2024). There also will be a KubeCon India in December. Proposed Solution: I suggest removing the past KubeCon Europe and adding KubeCon Hong Kong and KubeCon India to the page. I'm ready to make a relevant PR if/then this suggestion is approved. P.S. In the future, I think it would be great to elaborate a better solution with all needed future events listed in some kind of YAML and displayed automatically on the website depending on the current date. Page to Update:
/language en /sig docs
/triage accepted /retitle Stale KubeCon 2024 events at main page (it's not a bug to list upcoming events; the bug is that the list is stale)
hey Are you going to follow up with this? Or could I?
Hi I just created to resolve it. However, when this PR is finalised and approved, your help in promoting these changes to other localisations will be much appreciated!