jiebi/CodeConvo huggingface dataset:
Code change:
It's possible to configure `kubeadm join` with a configuration file instead of command line flags, and some more advanced features may only be available as configuration file options. This file is passed using the `--config` flag and it must <del> contain a `JoinConfiguration` structure. </del> <ins> contain a `JoinConfiguration` structure. Mixing `--config` with others flags may not be allowed in some cases. </ins> <del> To print the default values of `JoinConfiguration` run the following command: </del> <ins> The default configuration can be printed out using the [kubeadm config print](/docs/reference/setup-tools/kubeadm/kubeadm-config/) command. </ins> <del> ```shell kubeadm config print join-defaults ``` </del> <ins> If your configuration is not using the latest version it is **recommended** that you migrate using the [kubeadm config migrate](/docs/reference/setup-tools/kubeadm/kubeadm-config/) command. </ins> <del> For details on individual fields in `JoinConfiguration` see [the godoc](https://godoc.org/k8s.io/kubernetes/cmd/kubeadm/app/apis/kubeadm#JoinConfiguration). </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> ## {{% heading "whatsnext" %}}

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:
cpu: 100m memory: 100Mi ports: <del> - containerPort: 80 </del>  No newline at end of file <ins> - containerPort: 80 </ins>

Related discussion:
text: The yaml file in "Creating the Guestbook Frontend Deployment" uses an image no more available ( ) I solved the issue by using Here is the working version I used!
Hey Can you share us a pic of the solved issue here?
/kind bug
/triage accepted
/assign
Code change:
cpu: 100m memory: 100Mi ports: <del> - containerPort: 80 </del>  No newline at end of file <ins> - containerPort: 80 </ins>

Related discussion:
text: The image file download for the frontend- is currently failing. I fixed by changing it to: image: us-
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
This looks similar to issue(s) and I think it is a duplicate. /triage duplicate
Fixes are welcome; please visit to discuss and track that work.
Closing this issue, resolved by PR
/close
Closing this issue. <detailsIn response to : /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
Code change:
<ins> apiVersion: apps/v1 kind: Deployment metadata: name: patch-demo spec: replicas: 2 selector: matchLabels: app: nginx template: metadata: labels: app: nginx spec: containers: - name: patch-demo-ctr image: nginx tolerations: - effect: NoSchedule key: dedicated value: test-team </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 /area localization
/assign
/unassign
Code change:
* One or more machines running one of: - Ubuntu 16.04+ - Debian 9+ <del> - CentOS 7 - Red Hat Enterprise Linux (RHEL) 7 </del> <ins> - CentOS 7+ - Red Hat Enterprise Linux (RHEL) 7+ </ins> - Fedora 25+ - HypriotOS v1.0.1+ - Flatcar Container Linux (tested with 2512.3.0)

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 The site '' does not list RHEL 8 or CentOS 8 as a supported os. Only RHEL 7 / CentOS 7 is listed. Both os versions released over a year ago and Google provides a lot of guides for how to install Kubernetes on CentOS 8. Please a) add RHEL 8 / CentOS 8 to the list of supported platforms or b) if there is a reason for this, explain it on the website. Why is this needed It is confusing when only an old os version ist supported without any further explanation. Comments <!-- Any additional related comments that might help. Drawings/mockups would be extremely helpful (if required). --
it's a matter of users testing and confirming these distros work fine. if you have tested them feel free to send a pull request to update. /sig cluster-lifecycle /help
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 : it's a matter of users testing and confirming these distros work fine. if you have tested them feel free to send a pull request to update. /help </details
/triage accepted
/kind feature /retitle Document kubeadm for RHEL 8
I had a look at it and sent in a pull request for this. Add forward compatibility in RHEL / CentOS to the list of supported platforms.
/assign
Code change:
title: "Your Title Here" date: YYYY-MM-DD slug: text-for-URL-link-here-no-spaces <ins> author: > Author-1 (Affiliation), Author-2 (Affiliation), Author-3 (Affiliation) </ins> --- ```

Related discussion:
text: This is a Feature 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--What would you like to be The blog submission guidelines currently do not reflect the new format required for front matter, particularly the inclusion of author metadata. This discrepancy could lead to confusion and incorrect submissions from contributors who follow the outdated format. The existing guidelines need to be updated to reflect this change. Proposed Solution: Update the example front matter on the to demonstrate the correct format for including author metadata. Ensure that any related content, such as instructions or explanations surrounding the addition of author information, is also updated to reflect the new requirement. Reference of a published blog following the new format: Example of new format: Page to Update: Page URL: source: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--Additional Information: /language en /sig docs /area blog
/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 : /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
/priority backlog
/assign
Code change:
## Owner references in object specifications Dependent objects have a `metadata.ownerReferences` field that references their <del> owner object. A valid owner reference consists of the object name and a UID within the same namespace as the dependent object. Kubernetes sets the value of </del> <ins> owner object. A valid owner reference consists of the object name and a {{<glossary_tooltip text="UID" term_id="uid">}} within the same {{<glossary_tooltip text="namespace" term_id="namespace">}} as the dependent object. Kubernetes sets the value of </ins> this field automatically for objects that are dependents of other objects like ReplicaSets, DaemonSets, Deployments, Jobs and CronJobs, and ReplicationControllers. You can also configure these relationships manually by changing the value of

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:
persistentvolumeclaim/my-pvc created ``` <del> The `--recursive` flag works with any operation that accepts the `--filename,-f` flag such as: `kubectl {create,get,delete,describe,rollout} etc.` </del> <ins> The `--recursive` flag works with any operation that accepts the `--filename,-f` flag such as: `kubectl {create,get,delete,describe,rollout}` etc. </ins> The `--recursive` flag also works when multiple `-f` arguments are provided:

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: Line 143, the backquote is placed at wrong position. The flag works with any operation that accepts the flag such as: Line 456~457, it needs to change hugo code for the consistency with other documents Proposed Solution: Line 143: The flag works with any operation that accepts the flag such as: etc. Line 456~457: Learn about . See . Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--
/language en /assign
Code change:
flag `--service-account-extend-token-expiration=false`. Check [Bound Service Account Tokens](https://github.com/kubernetes/enhancements/blob/master/keps/sig-auth/1205-bound-service-account-tokens/README.md) for more details. <del> - `CheckpointContainer`: Enables the kubelet `checkpoint` API. </del> <ins> - `ContainerCheckpoint`: Enables the kubelet `checkpoint` API. </ins> See [Kubelet Checkpoint API](/docs/reference/node/kubelet-checkpoint-api/) for more details. - `ControllerManagerLeaderMigration`: Enables Leader Migration for [kube-controller-manager](/docs/tasks/administer-cluster/controller-manager-leader-migration/#initial-leader-migration-configuration) and

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:
background-repeat: no-repeat, repeat; background-size: auto 100%, cover; color: #fff; <del> width: 100vw; </del> /* fallback in case calc() fails */ padding: 5vw; padding-bottom: 1em;

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: Proposed Solution: Page to Update: /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
During my browsing of the docs on a mobile device, I came across a similar situation on another page, specifically in the . It seems this issue might be widespread and could be affecting multiple pages, not limited to just the community page. Perhaps we could explore identifying a CSS fix that enhances the rendering of pages with wider elements. This way, we can efficiently resolve the problem and improve the overall user experience.
/area web-development
I tried making some changes on the source, A simple overflow - x in the right places seems to solve the problem. ! However, I'd often come across such problems when the scaling isn't managed properly. I'm sure there are better ways to get this problem fixed.
I see, In that case I'll try to find anymore pages that might be having the same issue.
Similar issue is present in case study
Code change:
</p> <p>A Kubernetes cluster consists of two types of resources: <ul> <del> <li>The <b>Master</b> coordinates the cluster</li> </del> <ins> <li>The <b>Control Plane</b> coordinates the cluster</li> </ins> <li><b>Nodes</b> are the workers that run applications</li> </ul> </p>

Related discussion:
text: This is a Clean Up 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 Change to call the control plane a “control plane”, not a “master”. Why is this needed Kubernetes terms have changed: &hellip;however has not yet got that memo. This work would be part of The term “master” is unhelpful when it has connotations of being paired with “slave”. Comments Note that the diagrams also need revising at the same time (if need be, this could be 2 separate PRs that merge together). /language en /wg naming /kind cleanup
/assign
/triage accepted
Code change:
<!-- overview --> <del> このページでは、クラスター内のノードが使用している[コンテナランタイム](/docs/setup/production-environment/container-runtimes/)を確認する手順を概説しています。 </del> <ins> このページでは、クラスター内のノードが使用している[コンテナランタイム](/ja/docs/setup/production-environment/container-runtimes/)を確認する手順を概説しています。 </ins> クラスターの実行方法によっては、ノード用のコンテナランタイムが事前に設定されている場合と、設定する必要がある場合があります。 マネージドKubernetesサービスを使用している場合、ノードに設定されているコンテナランタイムを確認するためのベンダー固有の方法があるかもしれません。

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:
{{< comment >}} TODO: Add more information about return codes once CRI implementation have checkpoint/restore. This TODO cannot be fixed before the release, because the CRI implementation need <del> the Kubernetes changes to be merged to implement the new CheckpointContainer CRI API </del> <ins> the Kubernetes changes to be merged to implement the new ContainerCheckpoint CRI API </ins> call. We need to wait after the 1.25 release to fix this. {{< /comment >}}

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:
Atualmente, se algum sistema externo executou a rotação, apenas o conteúdo do arquivo de log mais recente estará disponível através de `kubectl logs`. Por exemplo, se houver um arquivo de 10MB, o `logrotate` executa a rotação e existem dois arquivos, um com 10MB de tamanho e um vazio, o `kubectl logs` retornará uma resposta vazia. {{< /note >}} <del> [cosConfigureHelper]: https://github.com/kubernetes/kubernetes/blob/{{< param "githubbranch" >}}/cluster/gce/gci/configure-helper.sh </del> <ins> [cosConfigureHelper]: https://github.com/kubernetes/kubernetes/blob/master/cluster/gce/gci/configure-helper.sh </ins> ### Logs de componentes do sistema

Related discussion:
text: This is a Bug Report Problem: Regarding , I found the similar broken links on other pages. English pages have already been fixed. ref: pt pages also need to be fixed. Proposed Solution: Fixes broken links including {{< param "githubbranch" }} to master. In the case of link to , fixes to {{< param "fullversion" }}. ref:
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
Code change:
[options_heading] other = "Opcje" <ins> [outdated_blog__message] other = "Ten artykuł jest starszy niż rok, więc część informacji może być już nieaktualnych. Upewnij się, że zawartość tej strony ciągle jest poprawna." [patch_release] other = "Patch Release" </ins> [post_create_issue] other = "Zgłoś problem"

Related discussion:
text: What would you like to be This issue is a follow-up task from displays some English text: ! To replace this text with localized strings, you can update with from . Specifically, these:
/language pl
/sig docs
/triage accepted