jiebi/CodeConvo huggingface dataset:
Change:
</td> <td> <p><code>tains</code> specifies the taints the Node API object should be registered with. <del> If this field is unset, i.e. nil, in the <code>kubeadm init</code> process it will be defaulted to <code>taints: [&quot;node-role.kubernetes.io/master:&quot;&quot;]</code>. If you don't want to taint your control-plane node, set this field to an empty slice, </del> <ins> If this field is unset, i.e. nil, in the <code>kubeadm init</code> process it will be defaulted with a control-plane taint for control-plane nodes. If you don't want to taint your control-plane node, set this field to an empty list, </ins> i.e. <code>taints: []</code> in the YAML file. This field is solely used for Node registration.</p> </td> </tr>

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: while cleaning up mentions of the legacy "master" taint in kubeadm docs: saw the following: it seems the generated reference API docs for kubeadm still include the "master" taint. Proposed Solution: cleanup mentions of the old taint from kubeadm's API reference docs at perhaps these need to be synced with: for dev-1.25 and main at k/website we removed the old taint from there before 1.24 was released. 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
/sig cluster-lifecycle /priority important-soon /kind cleanup
cc
Change:
<div class="row"> <div class="col-md-8"> <p><b>The Control Plane is responsible for managing the cluster.</b> The Control Plane coordinates all activities in your cluster, such as scheduling applications, maintaining applications' desired state, scaling applications, and rolling out new updates.</p> <del> <p><b>A node is a VM or a physical computer that serves as a worker machine in a Kubernetes cluster.</b> Each node has a Kubelet, which is an agent for managing the node and communicating with the Kubernetes control plane. The node should also have tools for handling container operations, such as containerd or Docker. A Kubernetes cluster that handles production traffic should have a minimum of three nodes.</p> </del> <ins> <p><b>A node is a VM or a physical computer that serves as a worker machine in a Kubernetes cluster.</b> Each node has a Kubelet, which is an agent for managing the node and communicating with the Kubernetes control plane. The node should also have tools for handling container operations, such as containerd or Docker. A Kubernetes cluster that handles production traffic should have a minimum of three nodes because if one node goes down, both an etcd member and a control plane instance are lost, and redundancy is compromised. You can mitigate this risk by adding more control plane nodes.</p> </ins> </div> <div class="col-md-4">

Discussion:
In Kubernetes Tutorials page- It is mentioned that a Kubernetes cluster that handles production traffic should have a minimum of three nodes. But there is no explanation provided as to why this is so. Suggestion to add a one-liner that a minimum of 3 master nodes is necessary for high availability.
/triage accepted
The label(s) cannot be applied, because the repository doesn't have them. <detailsIn response to : /kind improvements 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
The label(s) cannot be applied, because the repository doesn't have them. <detailsIn response to : /kind improvement 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:
コミュニティの誰かがすでに同じような質問をしている可能性があり、あなたの問題を解決できるかもしれません。 Kubernetesチームも[Kubernetesタグが付けられた投稿](https://stackoverflow.com/questions/tagged/kubernetes)を監視しています。 <del> もし役立つ既存の質問がない場合は、[新しく質問してみてください](https://stackoverflow.com/questions/ask?tags=kubernetes)。 </del> <ins> もし役立つ既存の質問がない場合は、[新しく質問する](https://stackoverflow.com/questions/ask?tags=kubernetes)前に、**[あなたの質問がStack Overflowのトピックに沿ったものであることを確認し](https://stackoverflow.com/help/on-topic)、[新しく質問する方法](https://stackoverflow.com/help/how-to-ask)のガイダンスに目を通してください！** </ins> ### Slack Kubernetesコミュニティの多くの人々は、Kubernetes Slackの`#kubernetes-users`チャンネルに集まっています。 <del> Slackは登録が必要です。[招待をリクエストする](https://slack.kubernetes.io)ことができ、登録は誰でも可能です）。 </del> <ins> Slackは登録が必要です。[招待をリクエストする](https://slack.kubernetes.io)ことができ、登録は誰でも可能です。 </ins> お気軽にお越しいただき、何でも質問してください。 登録が完了したら、WebブラウザまたはSlackの専用アプリから[Kubernetes organization in Slack](https://kubernetes.slack.com)にアクセスします。

Discussion:
This is a Feature Request What would you like to be We need to update according to the English text, because it is outdated. Why is this needed "Questions", "Stack Overflow" and "Bugs and feature requests" sections are outdated. Questions: Change the URL /docs/reference/kubectl/overview/ to /docs/reference/kubectl/ for . Stack Overflow: Update the statement for how to ask a new question. Bugs and feature requests: Change "Docker version" to "container runtime version". Comments /language ja
/triage accepted
/assign
Change:
HOSTNAME=envar-demo ... DEMO_GREETING=Hello from the environment <ins> DEMO_FAREWELL=Such a sweet sorrow </ins> 1. To exit the shell, enter `exit`.

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] --- [ ] Feature Request [X] Bug Report Problem: Documentation example for environment variables only shows one variable, so it is not clear to users how to add a second or subsequent variables Proposed Solution: Add a second variable to the example. Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional 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. Prevent issues from auto-closing with an comment. If this issue is safe to close now please do so with . Send feedback to sig-testing, kubernetes/test-infra and/or . /lifecycle stale
/remove-lifecycle stale /assign
Change:
1. The kubelet on a node self-registers to the control plane 2. You (or another human user) manually add a Node object <del> After you create a Node object, or the kubelet on a node self-registers, the </del> <ins> After you create a Node {{< glossary_tooltip text="object" term_id="object" >}}, or the kubelet on a node self-registers, the </ins> control plane checks whether the new Node object is valid. For example, if you try to create a Node from the following JSON manifest:

Discussion:
On line - Its better to clarify where node object is created. My assumption is on control panel (api server).
We could use a for “object”, so that you can click on that and confirm that objects are created in the API server. /kind feature /triage accepted /priority backlog
/retitle Explain meaning of “object” in Nodes concept /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 : /retitle Explain meaning of “object” in Nodes concept /help Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details
Hi, I would like to work on this issue. /assign
Change:
} <ins> @media only screen and (max-width: 840px) { section.call-to-action .main-section .cta-image.cta-image-before, section.call-to-action .main-section .cta-image.cta-image-after { order: 0; } section.call-to-action .main-section .cta-image > img { margin: 0; } section.call-to-action .main-section .cta-image > img { width: 7rem; } section.call-to-action .main-section > div.call-to-action > div { padding: 0 2rem 0 2rem; } section.call-to-action .main-section .cta-text { flex: 2 0 75vw; max-width: initial; padding: 5vw 0 0 0; } } </ins> /*  GO FULL WIDTH AT LESS THAN 480 PIXELS */ @media only screen and (max-width: 480px) { .col { margin: 1% 0 1% 0%;} <ins> .col-container { flex-direction: column; } </ins> } @media only screen and (max-width: 650px) {

Discussion:
This is feedback by email from within the CNCF/Linux Foundation: add the CKA/CKAD logos from to the page.
I'll take care of this, so assign it to me :)
/assign
Change:
`kubeadm upgrade node` does the following on worker nodes: - Fetches the kubeadm `ClusterConfiguration` from the cluster. <del> - Upgrades the kubelet configuration for this node. </del> <ins> - Upgrades the kubelet configuration for this node. </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--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:
{{< feature-state for_k8s_version="v1.21" state="deprecated" >}} {{< note >}} <del> この機能、特にアルファ版の`topologyKeys`APIは、Kubernetes v1.21以降では非推奨です。Kubernetes v1.21で導入された、[トポロジーを意識したヒント](/ja/docs/concepts/services-networking/topology-aware-hints/)が同様の機能を提供します。 </del> <ins> この機能、特にアルファ版の`topologyKeys`APIは、Kubernetes v1.21以降では非推奨です。Kubernetes v1.21で導入された、[トポロジーを意識したルーティング](/ja/docs/concepts/services-networking/topology-aware-routing/)が同様の機能を提供します。 </ins> {{</ note >}} *Serviceトポロジー*を利用すると、Serviceのトラフィックをクラスターのノードトポロジーに基づいてルーティングできるようになります。たとえば、あるServiceのトラフィックに対して、できるだけ同じノードや同じアベイラビリティゾーン上にあるエンドポイントを優先してルーティングするように指定できます。

Discussion:
This is a Feature Request What would you like to be The ja documents should be updated about Topology Aware Routing. (Related: ) Why is this needed The ja documents are outdated about Topology Aware Routing. Comments /language ja /assign
/triage accepted
Change:
width: 100% $toc-margin: 15px <del> $header-clearance: 40px </del> <ins> $header-clearance: $header-height + 20px </ins> * + h2, * + h3, * + h4, * + h5, * + h6 margin-top: 30px

Discussion:
For any section deeplink, the linked section title and some content is now obscured in the viewport by the floating header menu. Example: ! This occurs regardless of browser window width: ! Yay responsive design, but :cry: being able to actually read the content w/o scrolling.
Thanks to for the fix!
Change:
Pour télécharger une version spécifique, remplacez `$(curl -s https://dl.k8s.io/release/stable.txt)` avec la version spécifique. <del> Par exemple, pour télécharger la version {{< param "fullversion" >}} sur macOS, tapez : </del> <ins> Par exemple, pour télécharger la version {{< skew currentPatchVersion >}} sur macOS, tapez : </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. Rendez le binaire kubectl exécutable.

Discussion:
This is a Bug Report Problem: The param is deprecated. Proposed Solution: Replace the shortcode (French pages), for example with when possible and append when needed. Part of /language fr /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:
<li data-type="counter"><label class="metric_detail">Type:</label> <span class="metric_type">Counter</span></li> <li class="metric_labels_varying"><label class="metric_detail">Labels:</label><span class="metric_label">apiserver_id_hash</span></li><li class="metric_deprecated_version"><label class="metric_detail">Deprecated Versions:</label><span>1.30.0</span></li></ul> </div><div class="metric" data-stability="alpha"> <ins> <div class="metric_name">apiserver_encryption_config_controller_automatic_reloads_total</div> <div class="metric_help">Total number of reload successes and failures of encryption configuration split by apiserver identity.</div> <ul> <li><label class="metric_detail">Stability Level:</label><span class="metric_stability_level">ALPHA</span></li> <li data-type="counter"><label class="metric_detail">Type:</label> <span class="metric_type">Counter</span></li> <li class="metric_labels_varying"><label class="metric_detail">Labels:</label><span class="metric_label">apiserver_id_hash</span><span class="metric_label">status</span></li></ul> </div><div class="metric" data-stability="alpha"> </ins> <div class="metric_name">apiserver_envelope_encryption_dek_cache_fill_percent</div> <div class="metric_help">Percent of the cache slots currently occupied by cached DEKs.</div> <ul>

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: removed metric from the documented metrics for Kubernetes v1.30, but the metric is still collected for the API server (ref: and ). Proposed Solution: Reinstate the documentation for such metric. Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--Kubernetes Version: v1.30 <!--Additional Information:--
/sig instrumentation
/triage accepted
This metrics exists in the file generated by . Or there is a problem with the file generated by before. Let me generate the metrics file again and see. /assign
After I re-ran the script, some metrics were indeed missing (not just metrics ), it was a problem with the generated script, I will take a closer look.
Change:
1. Téléchargez la dernière version: ``` <del> curl -LO https://storage.googleapis.com/kubernetes-release/release/$(curl -s https://storage.googleapis.com/kubernetes-release/release/stable.txt)/bin/darwin/amd64/kubectl </del> <ins> curl -LO https://dl.k8s.io/release/$(curl -s https://dl.k8s.io/release/stable.txt)/bin/darwin/amd64/kubectl </ins> ``` <del> Pour télécharger une version spécifique, remplacez `$(curl -s https://storage.googleapis.com/kubernetes-release/release/stable.txt)` avec la version spécifique. </del> <ins> Pour télécharger une version spécifique, remplacez `$(curl -s https://dl.k8s.io/release/stable.txt)` avec la version spécifique. </ins> Par exemple, pour télécharger la version {{< param "fullversion" >}} sur macOS, tapez : ``` <del> curl -LO https://storage.googleapis.com/kubernetes-release/release/{{< param "fullversion" >}}/bin/darwin/amd64/kubectl </del> <ins> curl -LO https://dl.k8s.io/release/{{< param "fullversion" >}}/bin/darwin/amd64/kubectl </ins> ``` 2. Rendez le binaire kubectl exécutable.

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: There are still references to instead of is the correct advertised download host and will eventually move to be fastly shielding a fully community-owned bucket ref: Proposed Solution: Replace with Also replace any references with using if applicable. Page to Update: Assorted e.g. , <!--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
hi Not a problem, didn't see anyone assigned to this issue. I am unassigning myself and assigning it to you. /unassign
/assign
Hi, I found a small issue with your proposed changes regarding one of the URLs, which is mentioned twice in the file. While returns as expected, I am getting an nginx-rendered HTML page saying for the new command () instead. As I understand, it happens due to the redirect configured on the new web server. Thus, works fine for me (it returns as expected).
i see Let me update it, thanks your work
Just done, please review all of PRs
Thanks!
And yes: These will need to follow redirects, in the future the tentative plan is it will redirect to a CDN in front of a different bucket created in a fully project / SIG-K8s-Infra controlled GCP or AWS account. I would recommend for downloading with curl more generally, even in docs / usage for other hosts.
Change:
* [Running ZooKeeper, A CP Distributed System](/docs/tutorials/stateful-application/zookeeper/) <del> ## CI/CD Pipeline * [Set Up a CI/CD Pipeline with Kubernetes Part 1: Overview](https://www.linux.com/blog/learn/chapter/Intro-to-Kubernetes/2017/5/set-cicd-pipeline-kubernetes-part-1-overview) * [Set Up a CI/CD Pipeline with a Jenkins Pod in Kubernetes (Part 2)](https://www.linux.com/blog/learn/chapter/Intro-to-Kubernetes/2017/6/set-cicd-pipeline-jenkins-pod-kubernetes-part-2) * [Run and Scale a Distributed Crossword Puzzle App with CI/CD on Kubernetes (Part 3)](https://www.linux.com/blog/learn/chapter/intro-to-kubernetes/2017/6/run-and-scale-distributed-crossword-puzzle-app-cicd-kubernetes-part-3) * [Set Up CI/CD for a Distributed Crossword Puzzle App on Kubernetes (Part 4)](https://www.linux.com/blog/learn/chapter/intro-to-kubernetes/2017/6/set-cicd-distributed-crossword-puzzle-app-kubernetes-part-4) </del> ## Clusters * [AppArmor](/docs/tutorials/clusters/apparmor/)

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--CI/CD Pipeline utorials horribly out of date. Depends on kubernetes 1.6 Proposed Solution: I wish I had the time to work on this. Remove it or update it. Page to Update: Links to out of date tutirial: CI/CD Pipeline <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--
/kind cleanup /priority important-longterm /language en /help I recommend removing the section entirely, it is really out of date; also, even though the links are to external documentation the reference to Jenkins isn't really in the spirit of the policy.
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 : /kind cleanup /priority important-longterm /language en /help Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details
/retitle Tutorials overview links to outdated CI/CD Pipeline pages
/assign
Change:
### Changing the CPU Manager Policy <del> Since the CPU manger policy can only be applied when kubelet spawns new pods, simply changing from </del> <ins> Since the CPU manager policy can only be applied when kubelet spawns new pods, simply changing from </ins> "none" to "static" won't apply to existing pods. So in order to properly change the CPU manager policy on a node, perform the following steps:

Discussion:
First line of the above section has a typo. This should be "manager" instead of "manger".
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