Course contentsShow
← Cloud and Infrastructure
Lesson 1101 of 2,98922. Kubernetes ArchitectureFree lesson

Control Plane Components Introduction

Overview of the components that make up the Kubernetes control plane and their roles.

Control Plane Components Introduction

What you'll learn: You'll discover the core components that make up Kubernetes' control plane and understand what each one does to keep your cluster running smoothly.


What is the Control Plane?

Think of the Kubernetes control plane as the brain and nervous system of your cluster. Just as your brain makes decisions and coordinates your body's actions, the control plane manages the entire cluster — deciding where containers should run, monitoring their health, and responding to changes.

The control plane doesn't run your application workloads directly. Instead, it orchestrates everything behind the scenes, making sure the desired state you've defined (like "run 3 copies of my web app") matches reality.

The Core Components

The control plane consists of several specialized components, each with a specific job:

kube-apiserver — The front door of Kubernetes. Every request to create, update, or query cluster resources goes through the API server. It's the only component that talks directly to the cluster's database.

etcd — The cluster's memory. This distributed key-value store holds all cluster data — what pods should exist, their configurations, secrets, and current state.

kube-scheduler — The matchmaker. When a new pod needs to run, the scheduler picks the best worker node for it based on resource availability and constraints.

kube-controller-manager — The automation engine. It runs multiple controllers that watch the cluster state and work to make reality match your desired configuration (like maintaining the right number of replicas).

cloud-controller-manager — The cloud liaison. This optional component handles cloud-provider-specific tasks like managing load balancers or persistent volumes.

Key Takeaway: The Kubernetes control plane is composed of five specialized components that work together to manage cluster state, schedule workloads, and maintain your desired configuration — none of them run your actual application containers.