

Note: CRI-O by default uses systemd as its cgroup_manager (see /etc/crio/nf).
#INSTALL CONTROLPLANE UPGRADE#
If you cannot upgrade to version 1.20.4+, a workaround for this bug is to create an explicit mountpoint (added to fstab) for e.g. This affects both nested and un-nested setups. Warning: Users with rvice on a btrfs drive or subvolume running Kubernetes versions prior to 1.20.4 may be affected by a kubelet error, like:įailed to start ContainerManager failed to get rootfs info: failed to get device for dir "/var/lib/kubelet": could not find device with major: 0, minor: 25 in cached partitions map
#INSTALL CONTROLPLANE INSTALL#
To control a kubernetes cluster, install kubectl on the control-plane hosts and any external host that is supposed to be able to interact with the cluster.Īll nodes in a cluster (control-plane and worker) require a running instance of rvice. Install either containerd or cri-o to meet this dependency. When creating a Kubernetes cluster with the help of kubeadm, install kubeadm and kubelet on each node.īoth control-plane and regular worker nodes require a container runtime for their kubelet instances which is used for hosting containers. When manually creating a Kubernetes cluster install etcd AUR and the package group kubernetes-control-plane (for a control-plane node) and kubernetes-node (for a worker node). 6.2 Pods cannot communicate when using Flannel CNI and systemd-networkd.
