Kubernetes architecture (control plane and nodes) - Time & Space Complexity

Time Complexity: Kubernetes architecture (control plane and nodes)

O(p x n)

Understanding Time Complexity

We want to understand how the work done by Kubernetes grows as we add more nodes and workloads.

How does the system handle more tasks and keep everything running smoothly?

Scenario Under Consideration

Analyze the time complexity of the control plane managing nodes.

apiVersion: v1
kind: Pod
metadata:
  name: example-pod
spec:
  containers:
  - name: example-container
    image: nginx
  nodeSelector:
    disktype: ssd

This snippet schedules a pod to a node with a specific label, showing how the control plane selects nodes.

Identify Repeating Operations

Look at what repeats when scheduling pods.

• Primary operation: The scheduler checks all nodes to find a match for the pod's requirements.
• How many times: It does this for each pod and each node available.

How Execution Grows With Input

As the number of nodes or pods grows, the scheduler's work grows too.

Input Size (n)	Approx. Operations
10 nodes, 10 pods	~100 checks (each pod checks nodes)
100 nodes, 100 pods	~10,000 checks
1000 nodes, 1000 pods	~1,000,000 checks

Pattern observation: The work grows quickly as both pods and nodes increase.

Final Time Complexity

Time Complexity: O(p × n)

This means the scheduler's work grows proportionally to the number of pods times the number of nodes.

Common Mistake

[X] Wrong: "The scheduler only checks one node per pod, so it's always fast."

[OK] Correct: The scheduler must consider all nodes to find the best fit, so work grows with nodes and pods.

Interview Connect

Understanding how Kubernetes scales helps you explain system behavior and design choices clearly.

Self-Check

"What if the scheduler used caching to remember node states? How would that affect the time complexity?"

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