jiebi/CodeConvo huggingface dataset:
Code change:
It's possible to configure `kubeadm init` with a configuration file instead of command line flags, and some more advanced features may only be available as <del> configuration file options. This file is passed with the `--config` option. </del> <ins> configuration file options. This file is passed using the `--config` flag and it must contain a `ClusterConfiguration` structure and optionally more structures separated by `---n` Mixing `--config` with others flags may not be allowed in some cases. </ins> The default configuration can be printed out using the [kubeadm config print](/docs/reference/setup-tools/kubeadm/kubeadm-config/) command. <del> It is **recommended** that you migrate your old `v1beta1` configuration to `v1beta2` using </del> <ins> If your configuration is not using the latest version it is **recommended** that you migrate using </ins> the [kubeadm config migrate](/docs/reference/setup-tools/kubeadm/kubeadm-config/) command. <del> For more details on each field in the `v1beta2` configuration you can navigate to our [API reference pages](https://godoc.org/k8s.io/kubernetes/cmd/kubeadm/app/apis/kubeadm/v1beta2). </del> <ins> For more information on the fields and usage of the configuration you can navigate to our API reference page and pick a version from [the list](https://godoc.org/k8s.io/kubernetes/cmd/kubeadm/app/apis/kubeadm#pkg-subdirectories). </ins> ### Adding kube-proxy parameters {#kube-proxy}

Related discussion:
text: It is very difficult to find any links to the . This is a huge roadblock to new users trying to do anything custom with kubeadm. As a new user, I don't expect to have to read about to find information about configuring the tool. To someone who is unfamiliar with the project, that seems like more advanced documentation than I should need, and therefore not somewhere I would expect to find basic config file documentation. I also was able to find the long before I found the more user-friendly documentation, which made it seem like that was the only documentation that exists. I would expect a link to those docs to be available on the kubeadm-config page, as well as where config files are mentioned in the kubeadm-init and kubeadm-join pages.
/language en
it seems you have missed these two sections: and for these commands the kubeadm API is actually the most important for. linking the command line reference page to the API makes sense. but instead of linking to a particular version of the API we should link to: and let users navigate to a particular API version. this is done with the idea that can also migrate v1beta1 -v1beta2. PRs welcome. thanks /sig cluster-lifecycle /priority backlog /help wanted
. I will keep most of the discussion over there for now.
/remove-help /assign /lifecycle-active sending a PR with:
Code change:
{{ if .HasShortcode "kat-button" }} <del> <div id="katacoda-environment" data-katacoda-ondemand="true" data-katacoda-port="30000" data-katacoda-env="minikube" data-katacoda-command="start.sh" data-katacoda-ui="panel"></div> </del> <ins> <div id="katacoda-environment" data-katacoda-ondemand="true" data-katacoda-port="30000" data-katacoda-env="minikube:1.20" data-katacoda-command="start.sh" data-katacoda-ui="panel"></div> </ins> {{ end }} {{ with .Site.Params.algolia_docsearch }} <!-- scripts for algolia docsearch -->

Related discussion:
text: 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 Minikube playground (pages such as ) launches Kubernetes v1.17 This is a shortcoming because there is drift between what we're documenting in pages like , and what actually works in the Katacoda environment. Proposed Solution: Update the Katacoda playground to use a newer version of Minikube and hence a newer Kubernetes cluster version. Page to Update: (and others that use the shortcode) Additional Information: /priority important-longterm
This causes:
/triage accepted
like this:] [URL of the embedded terminal] view- [Content of ] I digged these pages but could not find where to update to change the minikube & K8s version:
do you know / can you recommend someone who can help explain where we might open a PR to update this?
Let me find out for you. The person is away this week so expect a respond next week.
Was there an update on this? Would be happy to help get this updated if needed.
Sorry for the delay. It was caught up with other conversations. I've raised a PR in It will now use K8s 1.20 which is the latest available in Katacoda. I haven't tested the build yet but will do once ready and will update accordingly. Update: Tested the preview build and looks to be working as expected.
I was reffering to minkube version not kubernetes version. is it possible to re-open the this issue
It seems that you have already opened another PR that addresses the Minikube version of Katacoda issue.
Code change:
<code>string</code> </td> <td> <del> <p><code>ontrolPlaneEndpoint</code> sets a stable IP address or DNS name for the control plane; </del> <ins> <p><code>controlPlaneEndpoint</code> sets a stable IP address or DNS name for the control plane; </ins> It can be a valid IP address or a RFC-1123 DNS subdomain, both with optional TCP port. In case the <code>controlPlaneEndpoint</code> is not specified, the <code>advertiseAddress</code> + <code>bindPort</code> are used; in case the <code>controlPlaneEndpoint</code> is specified but without a TCP port,

Related discussion:
text: found typo "ontrolPlaneEndpoint" in the below <img width="862" alt="typo ontrolPlaneEndpoint" src=""There is a typo "ontrolPlaneEndpoint" in the localAPIEndpoint description it should be "controlPlaneEndpoint"
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
/retitle Typo in auto-generated "kubeadm Configuration (v1beta4)" reference page
The mentioned reference page for "kubeadm Configuration (v1beta4)" is . The page is generated from the upstream source code . As the page is generated from the upstream source code, any fixes would need to be addressed there. For those interested in contributing to resolve this issue, please refer to the upstream contribution guidelines outlined at:
/sig docs
this is not a typo in the code files and also in my browser it's shown as controlPlaneEndpoint, so maybe it's a rendering issue. ! cc
but again, there are no typos in the code / go docs. also NOTE that v1beta4 is WIP API that should not be used yet by users.
the in is also dropped in another place on that page, screenshot below. I'm not familiar with the autogeneration for these pages, is there some processing on the word that is dropping letters when converting from the original? Looks like in the source file its written with a capital and in the generated file its with a lower case. Not sure why it would only so it sometimes though. We should check to see if this is happening on other pages. /priority awaiting-more-evidence <img width="789" alt="Screenshot 2024-03-27 at 9 44 26 AM" src=""
Another interesting observation looking at the - it appears to only happen on the v1beta4 version of the docs, not the previous versions. Looks like it was modified with .
Put up a fix in . It looks like this wasn't from an autogeneration error and just a simple typo when the docs were updated for v1beta4.
Code change:
``` ```shell <del> kubectl get pods -l run=cattle -n=production </del> <ins> kubectl get pods -l app=cattle -n=production </ins> ``` ``` NAME                      READY     STATUS    RESTARTS   AGE

Related discussion:
text: 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: After creating and scaling deployment using command kubectl create deployment cattle -- kubectl scale deployment cattle --replicas=5 When we execute below command to list pods with options -l kubectl get pods -l run=cattle O/P is No resources found in production namespace. Proposed Solution: kubectl get pods -l app=cattle Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--
/assign
can you / have you confirmed that this is a bug? If so, it's be good to record this issue as /kind bug
Yes, this is a bug. When was changed to , the label should have changed from to . This needs to be updated on a couple of other pages as well. /kind bug
/priority backlog
Code change:
| `AnyVolumeDataSource` | `false` | Alpha | 1.18 | 1.23 | | `AnyVolumeDataSource` | `true` | Beta | 1.24 | | | `AppArmor` | `true` | Beta | 1.4 | | <del> | `CheckpointContainer` | `false` | Alpha | 1.25 | | </del> <ins> | `ContainerCheckpoint` | `false` | Alpha | 1.25 | | </ins> | `CPUManager` | `false` | Alpha | 1.8 | 1.9 | | `CPUManager` | `true` | Beta | 1.10 | | | `CPUManagerPolicyAlphaOptions` | `false` | Alpha | 1.23 | |

Related discussion:
text: Feature Gate ChecpointContainer is unrecognized by kubelet. I've tried to set up a new 1.25 cluster with kubeadm with kubelet config And it fails with I've also tried to set up another cluster without this feature gate and enable it after, and it goes the same. Kubelet is started and checkpoint api is accessible. To reproduce try to install a new cluster with kubeadm v1.25.0 and use next kubelet config Or try to enable this feature gate on already installed 1.25.0 cluster No response <details</details<detailsBare Metal </details<details</details<detailskubeadm 1.25.0 </details<detailscontainerd </details<details</details
This issue is currently awaiting triage. If a SIG or subproject determines this is a relevant issue, they will accept it by applying the label and provide further guidance. 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
The feature gate name is according to
/sig node
/kind documentation
doesn't list a feature gate for kubelets. has a feature gate named . I'm guessing that this is a docs bug and is incorrect (possibly other docs pages too).
Thank you Yep, using as feature gate name resolves the issue. So this is a doc bug.
/retitle Feature gate misnamed in docs
/transfer website
This issue is now and should fix it. /language en /triage accepted
/sig docs
/priority backlog
Code change:
managing controller to process any [finalizer rules](/docs/concepts/overview/working-with-objects/finalizers/) for the resource. {{<glossary_tooltip text="Finalizers" term_id="finalizer">}} prevent accidental deletion of resources your cluster may still need to function <del> correctly. For example, if you try to delete a `PersistentVolume` that is still </del> <ins> correctly. For example, if you try to delete a [PersistentVolume](/docs/concepts/storage/persistent-volumes/) that is still </ins> in use by a Pod, the deletion does not happen immediately because the `PersistentVolume` has the `kubernetes.io/pv-protection` finalizer on it. <del> Instead, the volume remains in the `Terminating` status until Kubernetes clears </del> <ins> Instead, the [volume](/docs/concepts/storage/volumes/) remains in the `Terminating` status until Kubernetes clears </ins> the finalizer, which only happens after the `PersistentVolume` is no longer bound to a Pod.

Related discussion:
text: This is a Feature Request What would you like to be There are terms that can use the addition of a glossary tooltip to show the meaning of the said term. Some terms can add into What's next section like: ReplicaSets, DaemonSets, Deployments, Jobs and CronJobs, and ReplicationControllers. Why is this needed This will enhance user experience and bring more clarity and less confusion. Comments Page to update:
/sig docs /language en /assign
This issue is fixed here .
IMO this is an acceptable change but I'd like another org member to chime in
/triage accepted
Hi Thanks for sharing your feedback and triage accepted.
Code change:
``` ```shell <del> kubectl get pods -l run=snowflake </del> <ins> kubectl get pods -l app=snowflake </ins> ``` ``` NAME                         READY     STATUS    RESTARTS   AGE

Related discussion:
text: 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: After creating and scaling deployment using command kubectl create deployment cattle -- kubectl scale deployment cattle --replicas=5 When we execute below command to list pods with options -l kubectl get pods -l run=cattle O/P is No resources found in production namespace. Proposed Solution: kubectl get pods -l app=cattle Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--
/assign
can you / have you confirmed that this is a bug? If so, it's be good to record this issue as /kind bug
Yes, this is a bug. When was changed to , the label should have changed from to . This needs to be updated on a couple of other pages as well. /kind bug
/priority backlog
Code change:
<a target="_blank" rel="noopener" href="https://stackoverflow.com/questions/tagged/kubernetes"> Stack Overflow</a>. <del> {{ T "layouts_docs_partials_feedback_issue" }} </del> <ins> {{ T "layouts_docs_partials_feedback_issue" | markdownify }} </ins> <a class="feedback--link" target="_blank" rel="noopener" href="https://github.com/kubernetes/website/issues/new?title=Issue%20with%20k8s.io"> {{ T "layouts_docs_partials_feedback_problem" }}</a>

Related discussion:
text: 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. --I want to add a hyperlink to the "GitHub repo". ! Comments <!-- Any additional related comments that might help. Drawings/mockups would be extremely helpful (if required). --Link to be :
/sig docs
/language en /triage needs-information
Hi Could you please describe on which page of the documentation you are facing issue?
This is under the feedback section of too many pages. We have to change all of them.
I think we need not change much here, A slight change in i18n markdown should do the trick
/assign I'll do that
/remove-triage needs-information
Thanks for raising the PR . Also, Please focus on those issues first which have label.
/triage accepted /priority backlog
Code change:
## {{% heading "prerequisites" %}} <del> Kubernetesの[コンテナランタイムの要件](/docs/setup/production-environment/container-runtimes)を熟知している必要があります。 </del> <ins> Kubernetesの[コンテナランタイムの要件](/ja/docs/setup/production-environment/container-runtimes)を熟知している必要があります。 </ins> <!-- steps --> ## コンテナランタイムのcgroupドライバーの設定 <del> [Container runtimes](/docs/setup/production-environment/container-runtimes)ページでは、kubeadmベースのセットアップでは`cgroupfs`ドライバーではなく、`systemd`ドライバーが推奨されると説明されています。 </del> <ins> [コンテナランタイム](/ja/docs/setup/production-environment/container-runtimes)ページでは、kubeadmベースのセットアップでは`cgroupfs`ドライバーではなく、`systemd`ドライバーが推奨されると説明されています。 </ins> このページでは、デフォルトの`systemd`ドライバーを使用して多くの異なるコンテナランタイムをセットアップする方法についての詳細も説明されています。 <del> ## kubelet cgroupドライバーの設定 </del> <ins> ## kubelet cgroupドライバーの設定 {#configuring-the-kubelet-cgroup-driver} </ins> kubeadmでは、`kubeadm init`の際に`KubeletConfiguration`構造体を渡すことができます。

Related discussion:
text: 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. --Update Japanese translation Why is this needed Comments <!-- Any additional related comments that might help. Drawings/mockups would be extremely helpful (if required). --ref. /language ja
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
I want to work on this. Have you already started working on it? It seems that some pages linked from here are not translated yet: dockershim-removal template For now, I'm going to start working on dockershim related contents. Feel free to notify me if this conflicts with your work.
I'll assign myself since you haven't assigned youself to this issue. Please tell me if this conflicts with you work. /assign
Code change:
<ins> apiVersion: batch/v1 kind: Job metadata: name: 'indexed-job' spec: completions: 5 parallelism: 3 completionMode: Indexed template: spec: restartPolicy: Never containers: - name: 'worker' image: 'docker.io/library/busybox' command: - "rev" - "/input/data.txt" volumeMounts: - mountPath: /input name: input volumes: - name: input downwardAPI: items: - path: "data.txt" fieldRef: fieldPath: metadata.annotations['batch.kubernetes.io/job-completion-index'] </ins>  No newline at end of file

Related discussion:
text: 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
/triage accepted
Code change:
## コンテナイメージ [コンテナイメージ](/docs/concepts/containers/images/)はすぐに実行可能なソフトウェアパッケージで、アプリケーションの実行に必要なものをすべて含んています。コードと必要なランタイム、アプリケーションとシステムのライブラリ、そして必須な設定項目のデフォルト値を含みます。 <del> 設計上、コンテナは不変で、既に実行中のコンテナのコードを変更することはできません。コンテナ化されたアプリケーションがあり変更したい場合は、変更を含んだ新しいコンテナをビルドし、コンテナを再作成して、更新されたイメージから起動する必要があります。 </del> <ins> 設計上、コンテナは不変で、既に実行中のコンテナのコードを変更することはできません。コンテナ化されたアプリケーションがあり変更したい場合は、変更を含んだ新しいイメージをビルドし、コンテナを再作成して、更新されたイメージから起動する必要があります。 </ins> ## コンテナランタイム

Related discussion:
text: 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 follow v1.19 of the original (English) text. Why is this needed is outdated. Comments /language ja /good-first-issue File to update Original diff between translated and v1.19 Note Currently, we use dev-1.19-ja.1 branch. Please open a PR targeting the branch. ref If you have a question, feel free to ask us at #kubernetes-docs-ja channel.
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 Feature Request <!-- See for guidance on writing an actionable issue description. --Update to follow v1.19 of the original (English) text. is outdated. /language ja /good-first-issue Currently, we use dev-1.19-ja.1 branch. Please open a PR targeting the branch. 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
/triage accepted
/assign
Code change:
kind: Ingress metadata: name: example-ingress <del> annotations: nginx.ingress.kubernetes.io/rewrite-target: /$1 </del> spec: ingressClassName: nginx rules:

Related discussion:
text: 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 example Ingress contains rewrite annotation: But with new ingress 0.22 + capture groups must be explicit, see As result this example rewrites all paths with / - it does work for simple example, but it breaks any more complex web service! So if some body uses it as template and edits it for his own use case, can get into trouble, which are bit tricky to detect. Proposed Solution: Just delete rewrite-target annotation and ingress will work as expect by default. Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--
issue page: /language en
Starting in Version 0.22.0, ingress definitions using the annotation are not backwards compatible with previous versions. In Version 0.22.0 and beyond, any substrings within the request URI that need to be passed to the rewritten path must explicitly be defined in a capture group. As this is simple ingress example so no rewrite example is needed
/triage accepted
/assign
Code change:
<ins> --- title: Add-ons - (Complementos) id: addons date: 2023-07-20 full_link: /es/docs/concepts/cluster-administration/addons/ short_description: > Son recursos que amplían la funcionalidad de Kubernetes. aka: tags: - tool --- Son recursos que amplían la funcionalidad de Kubernetes. <!--more--> [Instalar complementos](/es/docs/concepts/cluster-administration/addons/) explica más sobre el uso de complementos con tu clúster y lista algunos complementos populares. </ins>

Related discussion:
text: This is a Feature Request What would you like to be Localize to Spanish Why is this needed There is no Spanish localization for this file. Comments /triage accepted /kind feature /language es /sig docs
/assign
GitHub didn't allow me to assign the following users: nilofe. Note that only with read permissions, repo collaborators and people who have commented on this issue/PR can be assigned. Additionally, issues/PRs can only have 10 assignees at the same time. For more information please see <detailsIn response to : /assign 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
Assignment received work performed PR
/assign