Why Kubernetes architecture (control plane and nodes)? - Purpose & Use Cases

The Big Idea

What if you could control hundreds of computers like a single smart machine, without logging into each one?

The Scenario

Imagine you have dozens or hundreds of computers, each running different apps and services. You try to manage them all by logging into each one, starting or stopping apps manually, and checking if everything is working.

The Problem

This manual way is slow and confusing. You might forget to update some computers, apps could crash without you noticing, and fixing problems takes a lot of time. It's like trying to control a big orchestra without a conductor.

The Solution

Kubernetes architecture solves this by organizing your computers into a system with a control center (control plane) and workers (nodes). The control plane tells the nodes what to do, watches over them, and keeps everything running smoothly automatically.

Before vs After

✗ Before

ssh node1
start app
ssh node2
start app
... (repeat for each node)

✓ After

kubectl apply -f app-deployment.yaml
kubectl get pods
kubectl scale deployment app --replicas=5

What It Enables

With Kubernetes, you can easily manage many computers and apps at once, making your system reliable and scalable without extra manual work.

Real Life Example

A company running an online store uses Kubernetes to keep their website and services running smoothly, even when thousands of customers visit at the same time.

Key Takeaways

Manual management of many computers is slow and error-prone.

Kubernetes uses a control plane to automate and coordinate worker nodes.

This architecture makes managing apps easier, faster, and more reliable.

Practice

1. Which component of Kubernetes is responsible for deciding what runs and where?

easy

A. Container runtime

B. Node

C. Pod

D. Control plane

Solution

1. Step 1: Understand Kubernetes architecture roles

   The control plane manages the cluster and makes decisions about scheduling and managing workloads.

2. Step 2: Identify the component that schedules workloads

   The control plane includes the scheduler which decides what runs and where.

3. Final Answer:

   Control plane -> Option D

4. Quick Check:

   Control plane = workload decision maker [OK]

Hint: Control plane manages; nodes run workloads [OK]

Common Mistakes:

• Confusing nodes with control plane
• Thinking containers decide scheduling
• Mixing pods with control plane

2. Which of the following is a correct component of the Kubernetes control plane?

easy

A. etcd

B. kube-proxy

C. kubelet

D. containerd

Solution

1. Step 1: List control plane components

   Control plane includes etcd, kube-apiserver, kube-controller-manager, and kube-scheduler.

2. Step 2: Identify which option is part of control plane

   etcd stores cluster data and is part of the control plane.

3. Final Answer:

   etcd -> Option A

4. Quick Check:

   etcd = control plane data store [OK]

Hint: etcd stores data in control plane [OK]

Common Mistakes:

• Confusing kubelet as control plane
• Thinking kube-proxy is control plane
• Mixing container runtime with control plane

3. Given a Kubernetes cluster, which component runs on each node to ensure containers are running properly?

medium

A. kubelet

B. kube-apiserver

C. kube-scheduler

D. etcd

Solution

1. Step 1: Identify node components

   Nodes run components like kubelet and kube-proxy to manage containers and networking.

2. Step 2: Determine which component manages container lifecycle on nodes

   kubelet runs on each node and ensures containers are running as expected.

3. Final Answer:

   kubelet -> Option A

4. Quick Check:

   kubelet = node container manager [OK]

Hint: kubelet runs on nodes to manage containers [OK]

Common Mistakes:

• Confusing kube-apiserver as node component
• Thinking scheduler runs on nodes
• Mixing etcd with node components

4. You notice pods are not starting on a node. Which component should you check first for errors on that node?

medium

A. kube-scheduler

B. kubelet

C. kube-apiserver

D. etcd

Solution

1. Step 1: Understand pod startup process

   Pods are started and managed on nodes by the kubelet component.

2. Step 2: Identify component to check for node pod issues

   Since pods fail to start on a node, kubelet logs and status should be checked first.

3. Final Answer:

   kubelet -> Option B

4. Quick Check:

   kubelet manages pods on nodes [OK]

Hint: Check kubelet logs for node pod issues [OK]

Common Mistakes:

• Checking scheduler instead of kubelet
• Looking at etcd for node pod errors
• Confusing apiserver with node issues

5. In a Kubernetes cluster, if the control plane node fails, which of the following is true?

hard

A. New pods can still be scheduled on nodes

B. Nodes automatically become control planes

C. Existing pods continue running but no new scheduling occurs

D. All pods immediately stop running

Solution

1. Step 1: Understand control plane failure impact

   The control plane manages scheduling and cluster state but nodes run pods independently.

2. Step 2: Analyze pod behavior when control plane is down

   Existing pods keep running on nodes, but no new pods can be scheduled without control plane.

3. Final Answer:

   Existing pods continue running but no new scheduling occurs -> Option C

4. Quick Check:

   Control plane down = no new scheduling, pods run [OK]

Hint: Control plane down stops scheduling, not running pods [OK]

Common Mistakes:

• Thinking pods stop immediately
• Assuming nodes become control planes
• Believing new pods schedule without control plane