Skip to content

kubelet

kubelet is a primary node agent that runs on each worker node in a Kubernetes cluster.^[400-devops__06-Kubernetes__k8s-ithelp__Day3__README.md] It functions as a micro-application responsible for maintaining communication between the node and the [[Control Plane]].^[400-devops__06-Kubernetes__k8s-ithelp__Day3__README.md]

Functionality

The core responsibility of the kubelet is to ensure that containers described in Pod specs are running and healthy.^[400-devops__06-Kubernetes__k8s-ithelp__Day3__README.md] It acts as the interface between the [[Control Plane]] and the [[Container runtime]] (such as Docker or CRI-O), receiving instructions to execute operations on the node.^[400-devops__06-Kubernetes__k8s-ithelp__Day3__README.md]

Components and Services

To operate correctly, every node running the kubelet must also utilize the following services:

  • Container Runtime: The software responsible for running containers, such as Docker, rkt, or CRI-O^[400-devops__06-Kubernetes__k8s-ithelp__Day3__README.md].
  • kube-proxy: A network proxy that manages network communication for services, handling traffic forwarding and service discovery within the cluster^[400-devops__06-Kubernetes__k8s-ithelp__Day3__README.md].

Sources

  • 400-devops__06-Kubernetes__k8s-ithelp__Day3__README.md