Skip to content

Latest commit

 

History

History
39 lines (26 loc) · 1.45 KB

Setup_a_control_plane.md

File metadata and controls

39 lines (26 loc) · 1.45 KB

Setting up a control plane

Preparation

  1. OPTIONAL: If you want to add a network proxy, see Configuring a proxy

  2. cmtadm preflight-check HOSTNAME

  3. cmtadm prepare --control-plane HOSTNAME CLUSTER_NAME [[KUBERNETES_DISTRO=]KUBERNETES_VERSION]

    (KUBERNETES_DISTRO is optional; RKE2 will be used by default on openSUSE and SLES; kubeadm is the default on Debian, Ubuntu, and RHEL; KUBERNETES_VERSION is only necessary if you don't want to use the latest version of Kubernetes)

  4. [Wait until cmtadm prepare completes]

Create the cluster

  1. cmtadm setup-control-plane [CNI] [POD_NETWORK_CIDR]
  2. [Wait until cmtadm setup-control-plane completes]

Next steps

If you intend to add worker nodes to your cluster, continue to Setup a worker node; if you intend to use the control plane as a worker node, see Use the control plane as a worker node.

Use the control plane as a worker node

If you wish to use the control plane as a worker node, you can do so by removing the control plane taint.

cmtadm untaint-control-plane

Performance considerations

If you intend to create a large cluster (hundreds of worker nodes), especially if those nodes are running from virtual machines, it is recommended that you pass none as CNI. Once all worker nodes have been added you can then run cmtadm setup-cni with the CNI you want to use.