Kubernetes Made Simple, Part 2: What happens after kubectl apply

The second part of the 'Kubernetes Made Simple' series focuses on the internal processes of the orchestrator. The author details the lifecycle of an object within the cluster, explaining exactly what happens from the moment a kubectl apply command is sent until containers are actually running on nodes. The article covers the interaction of Control Plane components, such as the API server, the scheduler, and controllers, as well as the role of etcd in maintaining system state. Readers will learn how Kubernetes ensures declarative infrastructure management and how the system reacts to changes in YAML manifests. This material is useful for both aspiring DevOps engineers and developers looking to better understand cloud infrastructure principles and container orchestration mechanisms. The analysis helps demystify the 'magic' of Kubernetes and reveals the internal logic of a distributed system.