Change:
--- reviewers: - sig-cluster-lifecycle <del> title: Creating a single control-plane cluster with kubeadm </del> <ins> title: Creating a cluster with kubeadm </ins> content_type: task weight: 30 --- <!-- overview --> <del> <img src="https://raw.githubusercontent.com/kubernetes/kubeadm/master/logos/stacked/color/kubeadm-stacked-color.png" align="right" width="150px">The `kubeadm` tool helps you bootstrap a minimum viable Kubernetes cluster that conforms to best practices. In fact, you can use `kubeadm` to set up a cluster that will pass the [Kubernetes Conformance tests](https://kubernetes.io/blog/2017/10/software-conformance-certification). </del> <ins> <img src="https://raw.githubusercontent.com/kubernetes/kubeadm/master/logos/stacked/color/kubeadm-stacked-color.png" align="right" width="150px">Creating a minimum viable Kubernetes cluster that conforms to best practices. In fact, you can use `kubeadm` to set up a cluster that will pass the [Kubernetes Conformance tests](https://kubernetes.io/blog/2017/10/software-conformance-certification). </ins> `kubeadm` also supports other cluster lifecycle functions, such as [bootstrap tokens](/docs/reference/access-authn-authz/bootstrap-tokens/) and cluster upgrades.

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: The title of used to be “Creating a single master cluster with kubeadm” and PR changed that to “Creating a single control-plane cluster with kubeadm” to match guidelines on terminology. However, the current title does not read as idiomatic English and could also mislead readers. All Kubernetes clusters should have exactly 1 control plane. You might have 0 control planes I suppose, in which case you need to fix that so that your workloads remain managed. You can't have 2 control planes for 1 cluster. What you can do is run your control plane across multiple hosts and even zones, to provide resilience. For that reason, it isn't the control plane that is single; instead, this page explains how to deploy a cluster where the control plane runs on only one computer. Proposed Solution: Change the title of the page. Pick wording that makes it clear that it's a simple cluster setup and isn't suitable for keeping your cluster within a low error budget (this is because if the one control plane host fails then you lose all control loops, the persisted data in etcd, and the Kubernetes cluster API). You don't need to go into all that detail so long as the reader is aware that another page explains how to do roughly the same thing but with availability taken into consideration. Also reword the following text from the body of the page: Optionally, add or revise introductory text to clarify the limitations of what this page is teaching. For example, consider if text “a minimum viable Kubernetes cluster that conforms to best practices” is the right fit? Page to Update: Additional Information: /sig cluster-lifecycle /language en /kind cleanup /priority backlog /good-first-issue If you're looking to pick this up as a first issue and would like advice, go ahead and reply - a Kubernetes contributor will help you to get started. Also, because this issue is not especially urgent, if you have already made a few contributions to this documentation, please consider leaving this one as a starting point for someone new.
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: The title of used to be “Creating a single control-plane cluster with kubeadm” and PR changed that to “Creating a single control-plane cluster with kubeadm” to match guidelines on terminology. However, the current title does not read as idiomatic English and could also mislead readers. Change the title of the page. Pick wording that makes it clear that it's a simple cluster setup and isn't suitable for keeping your cluster within a low error budget, because if the one control plane host fails then you lose all control loops, the persisted data in etcd, and the Kubernetes cluster API. /sig cluster-lifecycle /language en /kind cleanup /priority backlog /good-first-issue If you're looking to pick this up as a first issue and would like advice, go ahead and reply - a Kubernetes contributor will help you to get started. Also, because this issue is not especially urgent, if you have already made a few contributions to this documentation, please consider leaving this one as a starting point for someone new. 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
my vote goes for: "Creating a cluster with kubeadm" and the page should link to the HA guide which is an optional extension. Install a single control-plane Kubernetes cluster or high-availability cluster "Creating a minimum viable Kubernetes cluster that conforms to best practices", seems good to me. The HA guide link (link under "high-availability cluster") can be moved under "higher availabilty" in this sentence: "Use multiple control-plane nodes. You can read Options for Highly Available topology to pick a cluster topology that provides higher availabilty." it's currently a bullet item here:
I think I can help with this one, if it's OK /assign
Anyone is welcome to open a pull request that makes the changes suggested, or otherwise helps get the issue done.