Platform extension

As explained in Effective Platform Engineering

A platform extension is a cluster capability that extends the Kubernetes API by exposing a new resource type or developer-configurable experience.

A platform extension is a cluster capability that extends the Kubernetes API with a resource type or developer-configurable experience Kubernetes does not natively support. It expands the platform product while preserving a clear distinction from core platform services. section 8.2

Scale extension delivery deliberately:

• Keep extensions within the unified platform product organization during early delivery rather than distributing ownership immediately. section 8.2
• Consider transferring extension responsibility only after the platform is beyond MVP and adoption has reached meaningful scale. section 8.2
• Test responsibility changes between two platform domain teams before expanding the division of work. section 8.2
• Move toward separate release-orchestration pipelines as the number of services and extensions grows, while deployment automation remains local to the cluster. section 8.2

Figure 8.2 The easiest way to understand the difference is to focus on extensions. When deployed, an extension enables developers to provision a resource through the Kubernetes API that Kubernetes does not natively support.

Shows the defining user-facing effect: deploying an extension lets developers provision a resource through the Kubernetes API that Kubernetes does not natively support. section 8.2

How Effective Platform Engineering covers it

How deep it goes

Defines the API-facing role and deployment implications, but stops short of describing extension implementation internals.

Examples

Uses a non-native Kubernetes API resource as the defining example and contrasts extensions with platform services.

What it assumes

Assumes familiarity with Kubernetes platforms, services, deployment pipelines, MVP delivery, and organizational scaling.

What you can do after

Evaluate when to introduce extensions and how to stage their ownership and delivery across platform teams.

How it connects

Connects Kubernetes API resources with platform services, release orchestration, MVP adoption, and platform team boundaries.

liveBookmanning.com

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

Related concepts

• platform servicecontrasts with · A platform service is a centrally provided, reusable capability that supplies common functionality to multiple applications, services, teams, or systems.
• Kubernetes APIuses · The Kubernetes API is the programmatic interface through which clients and components define, query, modify, and manage Kubernetes resources and cluster state.
• pluginkind of · A plugin is an optional software component that extends or modifies a host application’s capabilities through an extension or integration mechanism.

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.