Emmes

Most Engineers use Kubernetes daily, but Cannot explain what happens when you run kubectl apply. Lets break it down. When you apply a manifest, here is what actually happens: - kubectl sends the YAML to the kube-apiserver - API server then validates the manifest, authenticates your request, and writes the desired state to etcd. - The scheduler watches for pods that are not assigned to any node. It scores available nodes, picks the best fit, and binds the pod to that node - The kubelet on that node sees the new pod assignment. It pulls the image, starts the container, and reports status back. - kube-proxy watches for service and endpoint changes. It updates iptables or IPVS rules so traffic can reach your pod Here is the interesting part. - The entire system is event-driven. No component polls others. - Each component watches the API server for changes and reacts only when needed. This is why Kubernetes is called a "desired state" system. You declare what you want. Kubernetes works in the background to make it happen. We break down the complete Kubernetes architecture and show what really happens behind the scenes when you run kubectl apply 𝗥𝗲𝗮𝗱 𝗶𝘁 𝗵𝗲𝗿𝗲: https://lnkd.in/gSB2GyXp #kubernetes #devops