🚨 kubectl Command: Behind the scenes!

When you perform kubectl apply, Kubernetes executes a series of steps to manage the desired state of the resources defined in the provided configuration files. Here’s on what happens:

1️⃣. User issues the kubectl apply -f request.

2️⃣. The kubectl tool sends an API request to the Kubernetes API server to create or update the resource.

3️⃣. The server validates the user’s request. If all looks good, the server will write the new or modified resource into etcd.

4️⃣. The kube-controller-manager is a daemon that continually watches the kube-apiserver.

5️⃣. It will be notified of the new deployment and proceeds to create new pods to achieve the desired state through another call to the kube-apiserver.

6️⃣. Then we have kube-scheduler which is responsible for scheduling Kubernetes pods on worker nodes.

7️⃣. The kube-scheduler is then notified about the new pods that have been created and proceeds to determine which nodes are valid placements for the same. The scheduler’s primary task is to identify the create request and choose the best node for a pod that satisfies the requirements.

8️⃣. Finally, Kubelet is an agent component that runs on every node in the cluster that gets notified if a pod has been assigned to it. The assigned node then coordinates with the container runtime on the node to start the appropriate containers.


❤️ 𝐅𝐨𝐥𝐥𝐨𝐰 @prodevopsguy 𝐟𝐨𝐫 𝐦𝐨𝐫𝐞 𝐬𝐮𝐜𝐡 𝐜𝐨𝐧𝐭𝐞𝐧𝐭 𝐚𝐫𝐨𝐮𝐧𝐝 𝐜𝐥𝐨𝐮𝐝 & 𝐃𝐞𝐯𝐎𝐩𝐬!!! // 𝐉𝐨𝐢𝐧 𝐟𝐨𝐫 𝐃𝐞𝐯𝐎𝐩𝐬 𝐃𝐎𝐂𝐬: @devopsdocs