liveBook · Manning

Controller manager

As explained in Google Anthos in Action

kube-controller-manager is the Kubernetes control-plane component that runs controllers to reconcile cluster resources toward their desired state.

The Kubernetes controller manager is a control loop that repeatedly compares resources with their requested state and drives them toward the declared state. section 3.2.2

A single binary runs separate threads for logical controllers. Controllers watch relevant API-server change events rather than receiving direct requests from the API server. section 3.2.2

The cloud controller manager is separate and appears only when configured for a cloud provider; it handles provider-specific nodes, routes, services, load balancers, filtering, and IP addresses. section 3.2.2

How Google Anthos in Action covers it

How deep it goes
Explains control-loop behavior, binary and thread structure, controller roles, and cloud-provider separation without deployment procedures.
Examples
Uses node status, Pod replication, Pod-to-Service endpoints, service accounts, routes, and cloud load balancers as controller responsibilities.
What it assumes
Assumes familiarity with Kubernetes resources, the API server, Pods, Services, and desired state.
What you can do after
Evaluate how Kubernetes preserves desired resource state and distinguish internal controllers from provider-specific controllers.
How it connects
Connects the API server, resource state, Pods, Services, replication, namespaces, and the cloud controller manager.

Also explained in

Compare how 2 books explain controller manager →

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Google Anthos in Action. The section links point to the parts of the book it draws on.