liveBook · Manning

Control plane

A control plane is the management and coordination part of a system that governs the configuration, policies, state, and operations of its components and resources.

How 10 Manning books explain it

Effective Platform Engineering

The control plane is the part of a distributed system that manages configuration, coordination, and lifecycle decisions for system resources.

How it is used
Coordinates platform infrastructure and extends desired-state orchestration to support resilient developer self-service.
How deep it goes
Works through an EKS base deployment and validation, while limiting that base to vendor-managed services rather than designing every platform component.
Examples
Uses an EKS base pipeline, Terraform cluster configuration, and tests for cluster status, nodes, and services.
What you can do after
Operate/configure it through a bounded EKS provisioning pipeline and validate the resulting cluster before extending the platform.

Read how Effective Platform Engineering explains control plane →

Acing the CCNA Exam: Volume 2 Advanced Networking and Security

The control plane is the set of network-device functions that determines the rules and state used by the data plane to forward traffic.

How it is used
Explains how network devices establish the rules and state that enable packet forwarding.
How deep it goes
Distinguishes control, data, and management planes, then contrasts distributed routing with centralized SDN control.
Examples
Uses OSPF route learning, ARP table construction, Syslog, NTP, SSH, and SDN controllers as examples.
What you can do after
Evaluate whether a function belongs to the control plane and distinguish distributed from centralized control.

Read how Acing the CCNA Exam: Volume 2 Advanced Networking and Security explains control plane →

Kafka for Architects

A service-mesh control plane is the centralized subsystem that configures, deploys, and manages the behavior of sidecar proxies and mesh-wide network policies.

How it is used
Centralizes configuration, coordination, health monitoring, and policy management while other components handle traffic or messages.
How deep it goes
Explains service-mesh responsibilities and Kafka controller internals through metadata logs, quorums, heartbeats, and request flows.
Examples
Uses Envoy, Istio, Linkerd, topic creation, partition assignments, broker heartbeats, and the __cluster_metadata log.
What you can do after
Operate/configure Kafka controllers or service-mesh proxies while separating centralized governance from message and service traffic.

Read how Kafka for Architects explains control plane →

Designing AI Systems

A control plane is the part of a distributed system responsible for deployment, configuration, operations, and management rather than handling application requests.

How it is used
Separates deployment and operational management from per-request execution in a distributed workflow service.
How deep it goes
Explains responsibilities, request-path boundaries, configuration flow, and asynchronous exceptions without detailing control-plane APIs.
Examples
Uses workflow containers, route registration, replica bounds, asynchronous job IDs, and parallel research sub-workflows.
What you can do after
Operate/configure workflow deployments by separating platform management, request execution, scaling, resources, and runtime reliability.

Read how Designing AI Systems explains control plane →

Kubernetes in Action, Second Edition

A control plane is the cluster-management component that makes decisions about and controls the operation of worker resources.

How it is used
Explains how Kubernetes turns multiple worker nodes into a uniform deployment area for applications.
How deep it goes
Defines the control plane, identifies its components and roles, and stops short of detailed component internals.
Examples
Uses control-versus-workload planes, a uniform deployment area, and API Server, etcd, Scheduler, and controller roles.
What you can do after
Evaluate Kubernetes cluster architecture by distinguishing management components from worker-node application execution.

Read how Kubernetes in Action, Second Edition explains control plane →

Designing AI Agents

A control plane is the part of a system that governs its operation by managing authoritative decisions, policies, or configuration.

How it is used
Governs agent execution through authoritative decisions, policies, and organizational controls rather than relying on memory or prompts alone.
How deep it goes
Describes control-plane components and accountability, and illustrates runtime enforcement with an atomic budget gate; tool-level listings do not implement that gate.
Examples
Uses an append-only decision ledger and a spending-cap gate with atomic reservations to illustrate authority and enforcement.
What you can do after
Evaluate control-plane boundaries and select governance controls proportional to an action’s credible effects.

Read how Designing AI Agents explains control plane →

Azure Security

A control plane action operates on the configuration or management of an Azure resource rather than on data stored within it.

How it is used
Separates Azure resource management from access to data stored within resources when designing RBAC permissions.
How deep it goes
Defines action categories, RBAC properties, and scope levels, but does not detail service-specific data-plane permissions.
Examples
Uses a Reader role on a storage-account resource group and an Azure CLI role-definition listing for virtual-machine permissions.
What you can do after
Apply via Azure RBAC by separating management permissions from data access and choosing a narrowly appropriate scope.

Read how Azure Security explains control plane →

Learn Docker in a Month of Lunches, Second Edition

A Kubernetes control plane is the set of management components that maintain cluster state and coordinate workloads.

How it is used
Coordinates workloads after kubectl submits a declarative application model to the Kubernetes cluster.
How deep it goes
Defines the management role and deployment flow but does not detail individual control-plane internals.
Examples
Uses Docker Desktop context selection and kubectl get nodes to verify cluster machines.
What you can do after
Operate/configure a cluster by submitting YAML through kubectl and checking its nodes.

Read how Learn Docker in a Month of Lunches, Second Edition explains control plane →

Cloud Observability in Action

The Kubernetes control plane is the set of Kubernetes components that expose the cluster API and maintain the desired state of cluster resources.

How it is used
Manages cluster resource state and exposes APIs and signals for operating Kubernetes workloads.
How deep it goes
Defines control-plane responsibilities and signal categories, but stops short of detailing individual control-plane components.
Examples
Uses API-server system logs and kubectl queries of API-server metrics, including admission-controller latency histograms.
What you can do after
Operate/configure Kubernetes observability by identifying control-plane signals and planning their collection, routing, storage, and querying.

Read how Cloud Observability in Action explains control plane →

Authorization in Action

A control plane is the set of interfaces and mechanisms used to define, configure, govern, and manage a system's behavior and infrastructure.

How it is used
Protects the mechanisms that define workflows, infrastructure, policies, and trust while permitting bounded operational work.
How deep it goes
Explains the operational boundary and demonstrates one Cedar restriction, while stopping short of broader implementation detail.
Examples
Uses an automation platform, predefined workflows, and a Cedar rule forbidding agents from changing automation definitions.
What you can do after
Configure agent permissions so operational actions remain available while control-plane modifications require authorized principals.

Read how Authorization in Action explains control plane →

Also covered in

What to know first

Related concepts

Questions about control plane

What is control plane?

A control plane is the management and coordination part of a system that governs the configuration, policies, state, and operations of its components and resources.

Which Manning books explain control plane?

Effective Platform Engineering, Acing the CCNA Exam: Volume 2 Advanced Networking and Security, Kafka for Architects, Designing AI Systems, Kubernetes in Action, Second Edition, Designing AI Agents, Azure Security, Learn Docker in a Month of Lunches, Second Edition and 2 more.

What should I know before learning control plane?

Manning books that teach control plane usually introduce container, distributed system, language model and load balancing first.

What is the difference between control plane and compute plane?

A control plane is the management and coordination part of a system that governs the configuration, policies, state, and operations of its components and resources. A compute plane is an execution layer that provides computational resources for running code and processing workloads.

What is control plane part of?

Control plane is part of service mesh. A service mesh is an infrastructure layer that manages communication between distributed services and commonly provides traffic control, security, and observability.

What are the parts of control plane?

Control plane includes kubernetes api server and damage limitation.

These guides are generated from the text of Manning books by Manning's knowledge graph and link to the sections they draw on. The full books are available on liveBook and at manning.com.