How Kubernetes Works: an editable mindmap
Explore How Kubernetes Works as an editable mindmap. Follow color-coded branches for Desired state, Scheduling, Worker nodes, Reconciliation, with supporting ideas and curved connections.
A mindmap of How Kubernetes Works, with the main ideas arranged around a central topic and connections that show how they relate.
How Kubernetes Works: an editable mindmap
The interactive MindMap canvas for this explanation — every lane, row and arrow above is a real QueryChart diagram you can open and edit.
How to read this mindmap
- Begin at “How Kubernetes Works” in the centre, then explore any branch that answers your question. The branch colors keep each group of ideas together.
- Curved lines show relationships; arrowheads appear only where one idea leads to another. Select any idea in the editor to change its text, position, or connections.
Desired state
This branch brings together “The manifest describes the TARGET, not the steps: “3 replicas of the API, image v2.1, port 8080”. Kubernetes figures out how to get there.”, “The control plane's API server is the front door. etcd is the cluster's source of truth — it holds the desired state everything else reconciles against.”.
Scheduling
This branch brings together “Scheduler watches and picks nodes for the pods”, “Scheduler assigns each pod to a healthy node”.
Worker nodes
This branch brings together “The kubelet is the worker's agent. It talks to the container runtime (usually containerd) to start the pods the scheduler assigns, and reports health back to the control plane.”, “A Service routes traffic to the running pods”.
Reconciliation
This branch brings together “Reconciliation is the core loop: compare current state to desired state, apply the difference, repeat. A crashed pod is replaced without human action.”, “Liveness and readiness probes decide health. A failing liveness probe restarts the pod; a failing readiness probe stops traffic to it.”, “Deployment stays at the desired state”.
Connections across the map
Kubernetes is declarative: you state the target, not the steps, and the system does the rest.
The control plane decides, the kubelet executes: nothing runs without the desired state in etcd.
Reconciliation is the loop: compare, apply the difference, repeat, forever.
Probes decide health, and health decides replacement: a failing pod is restarted without human action.
Kubernetes orchestrates the containers Docker packages, which is why the two visuals connect.
Key relationships and takeaways
- Kubernetes is declarative: you state the target, not the steps, and the system does the rest.
- The control plane decides, the kubelet executes: nothing runs without the desired state in etcd.
- Reconciliation is the loop: compare, apply the difference, repeat, forever.
- Probes decide health, and health decides replacement: a failing pod is restarted without human action.
- Kubernetes orchestrates the containers Docker packages, which is why the two visuals connect.
When to use this visual
- Explaining the control plane versus worker distinction to a team new to Kubernetes.
- Teaching the declarative model before someone writes their first Deployment and Service manifests.
- Grounding a conversation about self-healing: what Kubernetes fixes automatically and what still needs an operator.
How it works
Start at the central topic
Rename “How Kubernetes Works” if you want to adapt this map to a specific project or lesson.
Develop the branches
Edit the supporting ideas, then add examples and notes where a branch needs more detail.
Connect related ideas
Draw curved connections across branches; use an arrow only when the relationship has a direction.
Frequently asked questions
What is Kubernetes in simple terms?
Kubernetes is a system that runs containerised applications across a cluster of machines and keeps them running. You tell it what you want (how many copies of each application, which image, which ports) and it schedules the work onto machines, restarts failures, scales up and down, and routes traffic. The visual captures that as declare, schedule, run and maintain.
What is the control plane in Kubernetes?
The control plane is the set of components that make decisions about the cluster: the API server that accepts your manifests, etcd that stores the desired state, the scheduler that places pods, and the controllers that reconcile reality toward the desired state. It is the brain. The worker nodes are the muscle: each runs a kubelet that starts and monitors the pods assigned to it.
What does 'declarative' mean in Kubernetes?
It means you describe the target state instead of issuing commands to reach it. You apply a manifest saying "run three replicas"; Kubernetes figures out the steps and keeps taking them whenever reality drifts. If a pod dies, the controller creates a replacement to return to three: no human reruns a command. The manifest is the source of truth, and reconciliation is the mechanism.
How does Kubernetes keep applications healthy?
Through probes and the reconciliation loop. Liveness probes tell Kubernetes whether a container is alive: a failing liveness probe restarts it. Readiness probes tell it whether a pod can serve traffic: a failing readiness probe removes it from the Service. The controller compares the running state to the desired state and applies the difference continuously, which is the loop the "Pod is healthy?" decision in the visual represents.
Edit this mindmap in QueryChart
Open this mindmap as your own editable free canvas. Move ideas, add branches, and draw new connections.