Cloud Controller Manager
What you'll learn: How Kubernetes connects your cluster to cloud provider APIs to automatically manage cloud-specific infrastructure.
What Is the Cloud Controller Manager?
The cloud-controller-manager is a control plane component that embeds cloud-specific logic, allowing Kubernetes to interact directly with your cloud provider's APIs (AWS, Azure, GCP, etc.). It's essentially the bridge between Kubernetes and the cloud platform hosting your cluster.
Before cloud-controller-manager existed, cloud-specific code lived inside the main controller manager. Separating this logic allows Kubernetes core to remain cloud-agnostic while giving cloud providers flexibility to manage their own integrations.
How It Works
Think of cloud-controller-manager as a translator at the United Nations. Kubernetes speaks a standard language (declaring desired state), but each cloud provider has its own dialect (AWS API, Azure API, etc.). The cloud-controller-manager translates Kubernetes requests into cloud-specific actions.
It runs several cloud-specific controllers:
- Node controller: Validates that nodes exist in the cloud and updates node status if cloud VMs are deleted
- Route controller: Configures network routes in the cloud for pod-to-pod communication across nodes
- Service controller: Creates, updates, and deletes cloud load balancers when you create LoadBalancer-type Services
For example, when you create a LoadBalancer Service, the service controller tells AWS to provision an ELB, or tells Azure to create an Azure Load Balancer—all automatically.
Integration Benefits
The cloud-controller-manager enables powerful automation: deleting a cloud VM automatically marks the Kubernetes node as unavailable, or creating a Service automatically provisions real cloud infrastructure without manual intervention. This tight integration makes Kubernetes truly cloud-native.
Key Takeaway: The cloud-controller-manager acts as Kubernetes' liaison to cloud providers, translating cluster operations into cloud API calls to automate infrastructure like load balancers, routes, and node lifecycle management.