Skip to content

Improving the creating-clusters-baremetal tutorial in KubeOne docs #1858

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 2 commits into
base: main
Choose a base branch
from
Open
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Original file line number Diff line number Diff line change
Expand Up @@ -135,8 +135,8 @@ The following infrastructure requirements **must** be satisfied to successfully
provision a Kubernetes cluster using KubeOne:

* You need the appropriate number of instances dedicated for the control plane
* You need **even** number of instances with a minimum of **three** instances
for the Highly-Available control plane
* You need an **odd** number of instances with a minimum of **three** instances
for the highly-available control plane
* If you decide to use a single-node control plane instead, one instance is
enough, however, highly-available control plane is highly advised,
especially in the production environments
Expand Down Expand Up @@ -222,7 +222,7 @@ apiVersion: kubeone.k8c.io/v1beta2
kind: KubeOneCluster
name: bm-cluster
versions:
kubernetes: '1.29.4'
kubernetes: '1.32.3'
cloudProvider:
none: {}

Expand All @@ -233,7 +233,7 @@ controlPlane:
sshUsername: root
sshPrivateKeyFile: '/home/me/.ssh/id_rsa'
taints:
- key: "node-role.kubernetes.io/master"
- key: "node-role.kubernetes.io/control-plane"
effect: "NoSchedule"

staticWorkers:
Expand Down