Control plane components (API server, scheduler, controller manager, etcd) in Kubernetes - Time & Space Complexity

Time Complexity: Control plane components (API server, scheduler, controller manager, etcd)

O(n)

Understanding Time Complexity

We want to understand how the work done by Kubernetes control plane components grows as the cluster size increases.

How does adding more nodes or pods affect the control plane's processing time?

Scenario Under Consideration

Analyze the time complexity of the following simplified control loop in the controller manager.

for each resource in clusterResources {
  desiredState = getDesiredState(resource)
  currentState = getCurrentState(resource)
  if (desiredState != currentState) {
    updateResource(resource, desiredState)
  }
}
    

This loop checks all resources and updates them if needed to match the desired state.

Identify Repeating Operations

Look for repeated actions in the code.

• Primary operation: Looping over all cluster resources to compare and update states.
• How many times: Once per resource, so the number of times equals the number of resources.

How Execution Grows With Input

As the number of resources grows, the controller manager must check each one.

Input Size (n)	Approx. Operations
10	10 checks and possible updates
100	100 checks and possible updates
1000	1000 checks and possible updates

Pattern observation: The work grows directly with the number of resources.

Final Time Complexity

Time Complexity: O(n)

This means the control plane work increases in a straight line as the cluster grows.

Common Mistake

[X] Wrong: "The control plane work stays the same no matter how many resources exist."

[OK] Correct: Each resource needs checking, so more resources mean more work.

Interview Connect

Understanding how control plane components scale helps you explain cluster performance and troubleshooting in real setups.

Self-Check

"What if the controller manager used caching to avoid checking all resources every time? How would the time complexity change?"

Practice

1. Which component of the Kubernetes control plane acts as the main entry point for all REST commands and handles communication with the cluster?

easy

A. etcd

B. Scheduler

C. API server

D. Controller manager

Solution

1. Step 1: Understand the role of the API server

   The API server is the front door of the Kubernetes control plane. It receives REST requests and processes them.

2. Step 2: Compare with other components

   The scheduler assigns pods to nodes, the controller manager runs controllers, and etcd stores cluster data. None handle REST communication directly.

3. Final Answer:

   API server -> Option C

4. Quick Check:

   API server = main REST entry point [OK]

Hint: API server handles all REST requests to the cluster [OK]

Common Mistakes:

• Confusing scheduler with API server
• Thinking controller manager handles REST calls
• Assuming etcd processes API requests

2. Which of the following is the correct command to check the status of the Kubernetes scheduler component?

easy

A. kubectl get pods -n kube-system | grep scheduler

B. kubectl get nodes --show-scheduler

C. kubectl describe scheduler

D. kubectl get scheduler-status

Solution

1. Step 1: Identify how to check scheduler status

   The scheduler runs as a pod in the kube-system namespace, so checking pods there helps find it.

2. Step 2: Analyze each command

   kubectl get pods -n kube-system | grep scheduler lists pods in kube-system and filters for scheduler, which is correct. The other commands are invalid kubectl commands or do not exist.

3. Final Answer:

   kubectl get pods -n kube-system | grep scheduler -> Option A

4. Quick Check:

   Scheduler runs as pod, check pods in kube-system [OK]

Hint: Scheduler runs as pod; check pods in kube-system namespace [OK]

Common Mistakes:

• Using invalid kubectl commands
• Trying to describe scheduler directly
• Assuming scheduler is a node property

3. Given the following scenario: The Kubernetes scheduler fails to assign pods to nodes. Which control plane component is most likely responsible for detecting and fixing this issue automatically?

medium

A. API server

B. kubelet

C. etcd

D. Controller manager

Solution

1. Step 1: Understand the roles of components

   The controller manager runs controllers that watch cluster state and fix issues like unscheduled pods.

2. Step 2: Identify responsible component for fixing scheduling issues

   When scheduler fails, controller manager detects pods not assigned and may trigger rescheduling or alerts. API server only handles requests, etcd stores data, kubelet runs on nodes.

3. Final Answer:

   Controller manager -> Option D

4. Quick Check:

   Controller manager fixes cluster state issues [OK]

Hint: Controller manager fixes cluster state problems automatically [OK]

Common Mistakes:

• Confusing API server with controller manager
• Thinking etcd fixes issues
• Assuming kubelet manages scheduling

4. You notice that the etcd cluster is not storing new data correctly. Which of the following is the most likely cause and fix?

medium

A. etcd disk is full; free up disk space or increase storage

B. Scheduler is overloaded; scale scheduler pods

C. API server is down; restart the API server pods

D. Controller manager crashed; restart controller manager

Solution

1. Step 1: Identify symptoms related to etcd

   etcd stores cluster data. If it fails to store new data, disk space or storage issues are common causes.

2. Step 2: Match cause and fix

   API server, scheduler, and controller manager issues do not directly cause etcd storage failure. Disk full on etcd node is the likely cause; freeing space or increasing storage fixes it.

3. Final Answer:

   etcd disk is full; free up disk space or increase storage -> Option A

4. Quick Check:

   etcd storage issues = disk full fix [OK]

Hint: etcd storage issues often mean disk full; check storage first [OK]

Common Mistakes:

• Restarting unrelated components
• Ignoring disk space on etcd nodes
• Assuming scheduler affects etcd storage

5. You want to ensure high availability of the Kubernetes control plane. Which combination of components should you deploy in multiple replicas to avoid a single point of failure?

hard

A. Multiple schedulers and controller managers only

B. Multiple API servers and etcd nodes

C. Multiple etcd nodes only

D. Multiple API servers only

Solution

1. Step 1: Understand high availability needs

   High availability means no single point of failure. Both API servers and etcd store critical data and handle requests.

2. Step 2: Identify components to replicate

   API servers can run multiple replicas behind a load balancer. etcd must run as a cluster with multiple nodes for data safety. Scheduler and controller manager can be run as leader election but are less critical to replicate for HA.

3. Final Answer:

   Multiple API servers and etcd nodes -> Option B

4. Quick Check:

   HA = replicate API servers + etcd nodes [OK]

Hint: Replicate API servers and etcd for control plane high availability [OK]

Common Mistakes:

• Replicating only schedulers or controller managers
• Ignoring etcd clustering
• Assuming API server alone is enough