Control plane extension

As explained in Effective Platform Engineering

A control plane extension is an added capability that extends a system control plane's API or resource-management behavior beyond its existing functionality.

A control plane extension adds capabilities that extend a system control plane’s API or resource-management behavior beyond its existing functionality. In Kubernetes platforms, extensions provision or configure resources beyond the Kubernetes API, such as external infrastructure. section 8.4.1 section 8.6

Extensions differ from control plane services. Services collect, analyze, and return or forward cluster and application state; extensions change what users can provision or configure. Keeping the categories distinct clarifies ownership, delivery pipelines, and operational maintenance as the platform grows. section 8.0 section 8.1

Storage classes and external resources

Managed Elastic Block Store and Elastic File System storage classes can remain standard AWS-managed features. A new storage technology, or an extension of those features, becomes a control plane extension when it extends the Kubernetes API or lets users provision resources outside the cluster. section 8.4.1

A practical platform starts by orchestrating extensions through a dedicated pipeline alongside control plane services. This supports sandbox and production environments, enables testing before release, and reduces overlapping maintenance work while the platform serves early customers. section 8.0 section 8.1

Common control plane extensions include:

• Storage classes for additional storage technologies. section 8.4.1
• Ingress and gateway APIs, resiliency capabilities, and authentication or authorization. section 8.6
• Service meshes for gateway APIs, routing, traffic policies, and zero-trust networking. section 8.6

Figure 9.1 Practical examples of evolutionary scaling strategies for engineering platform components

Use the scaling strategies figure to compare when control plane extensions should support priorities such as public API gateway integration. section 9.0

How Effective Platform Engineering covers it

How deep it goes

Defines the category, contrasts it with services, and illustrates storage and gateway cases without detailing implementation internals.

Examples

Uses EBS and EFS storage classes, additional storage technologies, service meshes, and public API gateway integration.

What it assumes

Assumes familiarity with Kubernetes control planes, platform teams, and cluster-wide services.

What you can do after

Evaluate whether a capability belongs in an extension pipeline and prioritize it against platform scaling needs.

How it connects

Connects Kubernetes API, storage classes, ingress, gateway API, service mesh, resiliency, and authentication and authorization.

liveBookmanning.com

Read Effective Platform Engineering on liveBook Get the book at manning.com

Related concepts

• API gatewayuses · An API gateway is an intermediary that provides an entry point for client requests to backend APIs or services and routes or otherwise mediates those requests.
• Kubernetes APIimplements · The Kubernetes API is the programmatic interface through which clients and components define, query, modify, and manage Kubernetes resources and cluster state.
• control planepart of · 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.

This explainer was generated by Manning's knowledge graph from the text of Effective Platform Engineering. The section links point to the parts of the book it draws on.