liveBook · Manning

Kubernetes operator

As explained in Kubernetes for Developers

The operator pattern packages domain-specific operational logic in a controller that reconciles custom resources toward their desired state.

A Kubernetes operator extends Kubernetes when built-in resources cannot express a particular business rule or operational construct. It packages that logic behind a Kubernetes-style API, usually alongside a custom resource definition. section 1.2.2

Use an operator when:

  • A workload needs domain-specific business logic that Kubernetes does not provide. section 1.2.2
  • You need a new Kubernetes-style construct rather than ordinary stateless or stateful application deployment. section 1.2.2

How Kubernetes for Developers covers it

How deep it goes
Defines the extensibility role and custom-resource relationship, but does not explain controller implementation or reconciliation mechanics.
Examples
Uses business logic and unsupported constructs as application scenarios for custom Kubernetes APIs.
What you can do after
Evaluate whether custom Kubernetes APIs and operator patterns fit a workload beyond standard stateless or stateful deployment.
How it connects
Connects to custom resource definitions, Kubernetes-style APIs, stateless applications, and stateful applications.

Also explained in

Compare how 7 books explain Kubernetes operator →

Related concepts

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