jiebi/CodeConvo huggingface dataset:
Change:
different than {{< param "version" >}}, replace {{< param "version" >}} with the desired minor version in the command below. <del> ```bash # This overwrites any existing configuration in /etc/yum.repos.d/kubernetes.repo cat <<EOF | sudo tee /etc/yum.repos.d/kubernetes.repo [kubernetes] name=Kubernetes baseurl=https://pkgs.k8s.io/core:/stable:/{{< param "version" >}}/rpm/ enabled=1 gpgcheck=1 gpgkey=https://pkgs.k8s.io/core:/stable:/{{< param "version" >}}/rpm/repodata/repomd.xml.key EOF ``` </del> <ins> ```bash # This overwrites any existing configuration in /etc/yum.repos.d/kubernetes.repo cat <<EOF | sudo tee /etc/yum.repos.d/kubernetes.repo [kubernetes] name=Kubernetes baseurl=https://pkgs.k8s.io/core:/stable:/{{< param "version" >}}/rpm/ enabled=1 gpgcheck=1 gpgkey=https://pkgs.k8s.io/core:/stable:/{{< param "version" >}}/rpm/repodata/repomd.xml.key EOF ``` </ins> {{< note >}} To upgrade kubectl to another minor release, you'll need to bump the version in `/etc/yum.repos.d/kubernetes.repo` before running `yum update`. This procedure is described in more detail in [Changing The Kubernetes Package Repository](/docs/tasks/administer-cluster/kubeadm/change-package-repository/). {{< /note >}} <del> 1. Install kubectl using `yum`: </del> <ins> 2. Install kubectl using `yum`: </ins> <del> ```bash sudo yum install -y kubectl ``` </del> <ins> ```bash sudo yum install -y kubectl ``` </ins> {{% /tab %}} {{< /tabs >}}

Discussion:
The following tab has missing or duplicate content: Install using native package management
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
Page related to issue: /language en
/kind bug
The tabs don't seem to be working right in that page. Fixes are welcome. I am wary to triage this as Accepted though as I'm worried that the bug description is unclear.
In addition to the tab content, there seems to be an issue with the overall layout, which appears to be disrupted. This might have been unintentionally caused by the changes introduced in It's possible that this occurred because the release documentation deadline was approaching, leading us to merge it based on an older Netlify build preview instead of verifying it with the latest Netlify preview build.
I've opened to address and rectify this layout. /assign
There's a shortcoming around merges and Netlify. The preview from Netlify shows how the branch renders; it doesn't show (merge train style) how the site would look after the merge.
/assign
Change:
--- title: Tutorial Interativo - Explorando seu aplicativo weight: 20 <ins> headless: true toc_hide: true _build: list: never publishResources: false </ins> --- <!DOCTYPE html>

Discussion:
The terminal to use the interactive tutorials is using Katacoda, however, it was purchased by O'Reilly and is outside the domain that the terminal is using to run.
Hi You can ask support queries in channels.
Page related to issue: /language pt
/retitle [pt-br] Remove the obsolete online interactive tutorial from the page
For anyone willing to assist on this, please refer to PR for information regarding the implementation of similar changes carried out on the main website (i.e. English pages).
/good-first-isssue
/triage accepted /assign
/retitle [pt-br] Obsolete online interactive tutorial in the Using Minikube to Create a Cluster page /kind bug
Change:
Scalable tracking of network endpoints in a Kubernetes cluster. content_template: templates/concept <del> weight: 10 </del> <ins> weight: 15 </ins> ---

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: lists the EndpointSlice concept before Service. Although the , the current page about Service should come before the page about EndpointSlice, which is still beta and only partly activated by default. Proposed Solution: Revise the EndpointSlice page to have a that is higher than the Service page. See for the line that needs tweaking. Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--Kubernetes Version: v1.18 Additional Information: /language en
This request has been marked as suitable for new contributors. 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 : This is a Bug Report <!-- See for guidance on writing an actionable issue description. --Problem: lists the EndpointSlice concept before Service. Revise the EndpointSlice page to have a that is higher than the Service page. See for the line that needs tweaking. Kubernetes Version: v1.17 /language en /good-first-issue </details
This is a good first issue; if you've already had a pull request or two merged, I recommend leaving this one so that it's saved for a new contributor.
Thanks for triaging with an eye for new contributors!
I'd like to work on this issue, as a new contributor.
it'll be great to have your input Have you already seen
Yes, I've read the docs and signed CLA already.
Retract my application as it seem I haven't meet some of requirements described in
If it is okay, I would like to take this up. Thanks.
/assign
This also looks like maybe it affects the rendering of the main Kubernetes web page at also, actually -- under Features, EndpointSlices is listed before Service Topology (in fact EndpointSlices is the very first feature listed).
Thanks for pointing that out I will put that list in the same sequence as documentation. I am planning to work on it this weekend.
are you working on this issue? if not I would like to take this.

Please let me know
I planned to work on it during my break but couldn't find much time to tend to it. Please feel free to take this up. I will circle back to this issue on March 1 when I have some capacity to spare. Thanks.
/assign
Hi, I am back from my holidays. Are you still working on this issue or would you like me to take it forward? Thanks.
You please take it, Sent from my iPhone
/priority important-longterm
I noticed you were just working in this area - would you like to pick this issue up as well?
Sure. :) Tim Bannister <:
/assign Prasad Katti <: working in this area - would you like to pick this issue up as well? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub , or unsubscribe
Change:
a Hello world application by entering this command: ```shell <del> kubectl run node-hello --image=gcr.io/google-samples/node-hello:1.0 --port=8080 </del> <ins> kubectl create deployment node-hello --image=gcr.io/google-samples/node-hello:1.0 --port=8080 </ins> ``` <!-- steps -->

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: Proposed Solution: Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--
could you provide some more information about what isn't right with
Tim, I am getting this !
I think you're concerned about the deprecation warning Have I got that right? /triage needs-information
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
Stale issues rot after 30d of inactivity. Mark the issue as fresh with . Rotten issues close after an additional 30d of inactivity. If this issue is safe to close now please do so with . Send feedback to sig-testing, kubernetes/test-infra and/or . /lifecycle rotten
Rotten issues close after 30d of inactivity. Reopen the issue with . Mark the issue as fresh with . Send feedback to sig-testing, kubernetes/test-infra and/or . /close
Closing this issue. <detailsIn response to : Rotten issues close after 30d of inactivity. Reopen the issue with . Mark the issue as fresh with . /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
/reopen
/assign
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
Change:
[thirdparty_message_single_item] other = """&#128711; This item links to a third party project or product that is not part of Kubernetes itself. <a class="alert-more-info" href="#third-party-content-disclaimer">More information</a>""" [thirdparty_message_disclaimer] other = """<p>Items on this page refer to third party products or projects that provide functionality required by Kubernetes. The Kubernetes project authors aren't responsible for those third-party products or projects. See the <a href="https://github.com/cncf/foundation/blob/master/website-guidelines.md" target="_blank">CNCF website guidelines</a> for more details.</p><p>You should read the <a href="/docs/contribute/style/content-guide/#third-party-content">content guide</a> before proposing a change that adds an extra third-party link.</p>""" <ins> [thirdparty_message_vendor] other = """Items on this page refer to vendors external to Kubernetes. The Kubernetes project authors aren't responsible for those third-party products or projects. To add a vendor, product or project to this list, read the <a href="/docs/contribute/style/content-guide/#third-party-content">content guide</a> before submitting a change. <a href="#third-party-content-disclaimer">More information.</a>""" </ins> [ui_search_placeholder] other = "Search this site"

Discussion:
This is a Refactor request <!-- 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 overview page at is a bit out of date: no reference to I'm not convinced that the “Four Cs of cloud native security” model is useful for readers to learn Does not align with other CNCF documents, such as Proposed Solution: Either: remove outright migrate content from into several destinations (keep this brief but on-point) &hellip;and then redirect to Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--Additional Information: /sig docs /sig security /language en
If we keep the link to then we should update it to be as this is the English docs.
The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs. This bot triages issues and PRs according to the following rules: After 90d of inactivity, is applied After 30d of inactivity since was applied, is applied After 30d of inactivity since was applied, the issue is closed You can: Mark this issue or PR as fresh with Mark this issue or PR as rotten with Close this issue or PR with Offer to help out with [Issue Triage][1] Please send feedback to sig-contributor-experience at . /lifecycle stale [1]:
/remove-lifecycle stale /triage accepted
Also see
/assign
I'd appreciate a (fresh) review on .
Change:
## CLIリファレンス * [kubectl](/docs/reference/kubectl/overview/) - コマンドの実行やKubernetesクラスターの管理に使う主要なCLIツールです。 <del> * [JSONPath](/docs/reference/kubectl/jsonpath/) - kubectlで[JSONPath記法](https://goessner.net/articles/JsonPath/)を使うための構文ガイドです。 </del> <ins> * [JSONPath](/ja/docs/reference/kubectl/jsonpath/) - kubectlで[JSONPath記法](https://goessner.net/articles/JsonPath/)を使うための構文ガイドです。 </ins> * [kubeadm](/docs/reference/setup-tools/kubeadm/kubeadm/) - セキュアなKubernetesクラスターを簡単にプロビジョニングするためのCLIツールです。 ## コンポーネントリファレンス

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. --Translate reference/kubectl/jsonpath/ into Japanese. Why is this needed This page has not been translated. Comments <!-- Any additional related comments that might help. Drawings/mockups would be extremely helpful (if required). --/language ja /assign
/triage accepted
Change:
kubectl get pod private-reg ``` ## {{% heading "whatsnext" %}} * Learn more about [Secrets](/docs/concepts/configuration/secret/). * Learn more about [using a private registry](/docs/concepts/containers/images/#using-a-private-registry). * Learn more about [adding image pull secrets to a service account](/docs/tasks/configure-pod-container/configure-service-account/#add-imagepullsecrets-to-a-service-account).

Discussion:
This link "" appears to be broken in the line: " <your-registry-serveris your Private Docker Registry FQDN. ( for DockerHub) "
According to , the V1 API has been deprecated.
/triage accepted /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: > The container runtime is the software that is responsible for running containers.

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:
This annotation requires the [PodTolerationRestriction](/docs/reference/access-authn-authz/admission-controllers/#podtolerationrestriction) admission controller to be enabled. This annotation key allows assigning tolerations to a namespace and any new pods created in this namespace would get these tolerations added. <ins> ### scheduler.alpha.kubernetes.io/tolerationsWhitelist {#schedulerkubernetestolerations-whitelist} Example: `scheduler.alpha.kubernetes.io/tolerationsWhitelist: '[{"operator": "Exists", "effect": "NoSchedule", "key": "dedicated-node"}]'` Used on: Namespace This annotation is only useful when the (alpha) [PodTolerationRestriction](/docs/reference/access-authn-authz/admission-controllers/#podtolerationrestriction) admission controller is enabled. The annotation value is a JSON document that defines a list of allowed tolerations for the namespace it annotates. When you create a Pod or modify its tolerations, the API server checks the tolerations to see if they are mentioned in the allow list. The pod is admitted only if the check succeeds. </ins> ### scheduler.alpha.kubernetes.io/preferAvoidPods (deprecated) {#scheduleralphakubernetesio-preferavoidpods} Used on: Nodes

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 has alpha support for an annotation ; however, this is not registered or documented. Proposed Solution: register the annotation document it We can achieve both of these by updating with information about the annotation. Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--Additional Information: We should document this name even though WG Naming have recommended avoiding the term “whitelist”. After documenting it, the next step could be to deprecate the annotation, or to make a new, non-alpha annotation that has a different name. /language en /kind bug /sig scheduling /lifecycle frozen
Also see
/triage accepted
Relevant to
/assign
Are you working on this issue? Do you need any help?
yes I am working on it.
Need any help from my side?
No as of now
I don't see any updates; so unassigning you. Please feel free to assign, if you come back here again and are willing to work on /unassign
I found this issue while going through and trying to learn more about these annotations. I have raised a PR regarding same here: PTAL! Also, how to proceed with this?
Change:
If you have already created the cluster you must adapt it by doing the following: - Find and edit the `kubelet-config-{{< skew currentVersion >}}` ConfigMap in the `kube-system` namespace. In that ConfigMap, the `kubelet` key has a <del> [KubeletConfiguration](/docs/reference/config-api/kubelet-config.v1beta1/#kubelet-config-k8s-io-v1beta1-KubeletConfiguration) </del> <ins> [KubeletConfiguration](/docs/reference/config-api/kubelet-config.v1beta1/) </ins> document as its value. Edit the KubeletConfiguration document to set `serverTLSBootstrap: true`. - On each node, add the `serverTLSBootstrap: true` field in `/var/lib/kubelet/config.yaml` and restart the kubelet with `systemctl restart kubelet`

Discussion:
This is a Bug Report <!-- Thanks for filing an issue! Before submitting, please fill in the following information. --<!-- See for guidance on writing an actionable issue description. --<!--Required Information--Problem: Url selector #kubelet-config-k8s-io-v1beta1-KubeletConfiguration doesn't make a difference between: and Proposed Solution: Removing the selector from the URLs Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--
This issue is currently awaiting triage. SIG Docs takes a lead on issue triage for this website, but any Kubernetes member can accept issues by applying the label. The label can be by org members by writing in a comment. <detailsInstructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details
/language en
/assign
/retitle Problems with (generated) reference for kubelet configuration
Change:
* Lean about [RuntimeClass](/docs/concepts/containers/runtime-class/) and how you can use it to configure different Pods with different container runtime configurations. * Read about [Pod topology spread constraints](/docs/concepts/workloads/pods/pod-topology-spread-constraints/). <del> * Read about [PodDisruptionBudget](https://kubernetes.io/docs/concepts/workloads/pods/disruptions/) and how you can use it to manage application availability during disruptions. </del> <ins> * Read about [PodDisruptionBudget](/docs/concepts/workloads/pods/disruptions/) and how you can use it to manage application availability during disruptions. </ins> * Pod is a top-level resource in the Kubernetes REST API. The [Pod](/docs/reference/generated/kubernetes-api/{{< param "version" >}}/#pod-v1-core) object definition describes the object in detail.

Discussion:
This is a Bug Report <!-- Thanks for filing an issue! Before submitting, please fill in the following information. --<!-- See for guidance on writing an actionable issue description. --<!--Required Information--Problem: Line 260, should be removed from the link to PodDisruptionBudget: Read about [PodDisruptionBudget]() and how you can use it to manage application availability during disruptions. Proposed Solution: Read about [PodDisruptionBudget](/docs/concepts/workloads/pods/disruptions/) and how you can use it to manage application availability during disruptions. Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--/language en
/assign
Change:
1. Apply the frontend Service from the `frontend-service.yaml` file: <ins> <!--- for local testing of the content via relative file path kubectl apply -f ./content/en/examples/application/guestbook/frontend-service.yaml --> </ins> ```shell kubectl apply -f https://k8s.io/examples/application/guestbook/frontend-service.yaml ``` <del> <!--- for local testing of the content via relative file path kubectl apply -f ./content/en/examples/application/guestbook/frontend-service.yaml --> </del> 1. Query the list of Services to verify that the frontend Service is running: ```shell

Discussion:
4 ordered lists have wrong indexes. For example, the number below should be 3. ! Page to update: /language en /kind cleanup
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