You are not logged in.
in wiki: https://wiki.archlinux.org/index.php/Ku … stallation
mentioned that
When creating a Kubernetes cluster with the help of kubeadm, install kubeadm and kubelet on each node.
why control plane(master node) need kublet installed?
Both control-plane and regular worker nodes require a container runtime for their kubelet instances which is used for hosting containers. Install either containerd or cri-o to meet this dependency.
why control plane(master node) need container runtime installed?
Above two instruction seems not match as offcial architecure.
Last edited by csj (2020-12-10 09:05:01)
Offline
Please edit your post and remove the large image. See https://wiki.archlinux.org/index.php/Co … s_and_code
Instead, you can link to wherever you found it.
Offline
It's not. You should refer to kubernetes documentation on the subject, not archwiki.
Offline
I found the package group is a little confusing too:
kubernetes-control-plane contains kubelet
Last edited by csj (2020-12-10 09:05:34)
Offline
The Control Plane consists of a few software components which itself can be run and managed using kubelet instead of manually installed directly onto the machine.
In that case, all the machines part of your cluster require kubelet and a container runtime, not just the machines that function as worker nodes. Using kubeadm is also well documented on the K8S website; https://kubernetes.io/docs/setup/produc … l-kubeadm/
Aside from that, a machine set up to run the control plane can itself also function as a worker node if you either 1) have the control plane installed directly onto the machine and a kubelet on that same machine as a cluster member or 2) when you have the control plane running with kubelet and 'untaint' the master node to allow pods to be scheduled on the master node's kubelet.
For a live production environment you should keep these workloads separated though.
Last edited by Omar007 (2020-12-10 09:12:22)
Offline
