The Kubernetes Machine: From kubectl apply to Running Containers

What really happens when you run kubectl apply?

In Part 1 of this Kubernetes masterclass, we go far beyond basic definitions and trace how Kubernetes works as a distributed, API-driven control system.

You will learn how a YAML manifest moves through kubectl, the API server, authentication, authorization, admission, etcd, controllers, the scheduler, kubelet and the container runtime before finally becoming a running Pod.

This episode also explains the deeper ideas that make Kubernetes work:

• Desired state versus observed state
• Reconciliation loops
• spec versus status
• Watches and events
• Labels and selectors
• ReplicaSets and Deployments
• Scheduling decisions
• Pod lifecycle
• Owner references, finalizers and garbage collection
• Server-side apply and field ownership

By the end of this episode, you will be able to mentally replay the complete journey from user intent to a healthy running workload—and understand which component is responsible at every step.

Mental model:

Intent → Store → Observe → Reconcile

Full interview prep guides and scenario walkthroughs: DevOpsInterview.Cloud