Part 2: A developer who only wrote code looks into how Kubernetes works internally out of curiosity

This looks at how Kubernetes' core components work together to deploy and manage applications, using a restaurant analogy.

The API server acts as the manager who is the center of all communication, while etcd serves as the order ledger that records the status of all orders. The Controller Manager is like the head chef overseeing the kitchen, the Scheduler is the assigner who allocates the appropriate kitchen, Kubelet is the kitchen supervisor, and the Container Runtime can be compared to the cook who actually makes the dishes.

The application deployment process is as follows:

• The user writes a manifest file and passes it to the API server using the kubectl command.
• The API server stores the received content in etcd.
• Afterward, each component interacts organically to perform the work needed to maintain the state declared by the user.