Kubernetes 101 : Static pods and the kubelet service
The "non-static" pods:
The static pods:
The static pods are handled directly by the kubelet service.
The Kube-API can see the static pods, but it can't interact with them directly.
The kubelet service runs on all the nodes of the cluster, it is in charge of spawning the pods and interacting directly with the container runtime engine like docker, CRI-O or CoreOS rkt.
The kubelet also takes care of restarting static pods in case of failure.
the API-server doesn't manages static pods.
The files in the "--pod-manifest-path" could be a pod Yaml configuration file.
The "--pod-manifest-path" could be "/etc/kubernetes/kubelet" for example.
The kubelet goes regularly through the "--pod-manifest-path" directory and runs the configurations files there to create or delete the static pods.
After filling out the configuration file for the kubelet service "/usr/lib/systemd/system/kubelet.service" as below:
We could start the kubelet service using the below command:
Comments