liveBook · Manning

Custom resource definition

Also called CRDs

A CustomResourceDefinition is a Kubernetes API object that defines a custom resource type and its schema.

How 8 Manning books explain it

Acing the Certified Kubernetes Administrator Exam, Second Edition

A custom resource definition is a Kubernetes API object that defines a new custom resource type and its schema.

How it is used
Extends the Kubernetes API with resource types that operators can manage as part of running applications.
How deep it goes
Explains CRD fields, scope, installation, discovery, and CR creation; directs field inspection to kubectl explain rather than unpacking generated schemas.
Examples
Uses CloudNativePG installation, a PostgreSQL Cluster manifest, kubectl discovery commands, and cluster-status checks.
What you can do after
Operate/configure it by installing an operator’s CRDs, inspecting available fields, creating a custom resource, and verifying its resulting workload.

Read how Acing the Certified Kubernetes Administrator Exam, Second Edition explains custom resource definition →

Server-Side WebAssembly

A custom resource definition is a Kubernetes API declaration that extends the Kubernetes API with a new custom resource type.

How it is used
Extends Kubernetes so Wasm platforms can declare and orchestrate application-specific resources through familiar API workflows.
How deep it goes
Explains CRD registration, custom-resource application, operator reconciliation, and concrete SpinKube and wasmCloud deployment workflows.
Examples
Uses Crossplane databases, KubeVirt virtual machines, SpinKube resources, and a wasmCloud Application deployed with kubectl.
What you can do after
Operate/configure CRD-backed Wasm deployments with kubectl, Helm, SpinKube, and wasmCloud status or inspection commands.

Read how Server-Side WebAssembly explains custom resource definition →

Kubernetes in Action, Second Edition

A CustomResourceDefinition is a Kubernetes API object that extends the Kubernetes API with a new custom resource type.

How it is used
Extends the Kubernetes API for Gateway networking resources and operator-managed application resources.
How deep it goes
Explains installation, release channels, custom objects, reconciliation, and cleanup, but does not detail CRD schema implementation.
Examples
Uses Gateway API CRDs and a MongoDBCommunity CRD, with kubectl installation, inspection, reconciliation, and deletion commands.
What you can do after
Operate custom API types by installing CRDs, creating custom resources, inspecting them, and removing them during cleanup.

Read how Kubernetes in Action, Second Edition explains custom resource definition →

Designing Deep Learning Systems: A guide for software engineers

A Kubernetes API extension that defines a custom resource kind and its schema.

How it is used
Extends Kubernetes with declarative API objects that operators can reconcile into running services, pods, and other resources.
How deep it goes
Explains the desired-versus-observed state loop, resource provisioning, status updates, and pod failover without detailing schema fields.
Examples
Uses TFJob, PyTorchJob, MPIJob, and Argo Workflow objects to demonstrate training and workflow execution.
What you can do after
Operate/configure Kubernetes-native training and workflow systems by submitting CRD objects and inspecting reconciled resources and status.

Read how Designing Deep Learning Systems: A guide for software engineers explains custom resource definition →

Kubernetes for Developers

A custom resource definition is a Kubernetes API extension that introduces a new resource type with a user-defined schema.

How it is used
Extends Kubernetes when built-in resources cannot express particular business logic or application constructs.
How deep it goes
Explains the purpose of custom resource definitions and operator patterns but stops short of implementation details.
Examples
Uses unsupported business logic and new constructs as motivating cases, contrasting them with ordinary web application deployment.
What you can do after
Build it from scratch by creating a Kubernetes-style API for requirements that built-in Kubernetes resources do not support.

Read how Kubernetes for Developers explains custom resource definition →

Kargo in Action

A Kubernetes API extension that defines a new resource type and its schema for storing domain-specific objects.

How it is used
Extends Kubernetes’ API so Kargo can express its domain model as resources managed through familiar Kubernetes tooling.
How deep it goes
Defines the API-extension role and installation checks, but stops short of describing schema fields.
Examples
Uses Kargo CRD installation and kubectl checks for CRD presence, controller health, and RBAC.
What you can do after
Operate/configure Kargo by installing its CRDs and verifying their presence alongside controller health and RBAC.

Read how Kargo in Action explains custom resource definition →

Kafka for Architects

A custom resource definition is a Kubernetes API extension that declares a new resource type and its schema.

How it is used
Represents Kafka artifacts as Kubernetes resources within a GitOps-managed Kafka deployment.
How deep it goes
Traces the YAML-to-Git-to-operator reconciliation flow without detailing CRD schema design or controller implementation.
Examples
Uses YAML definitions for Kafka topics, connectors, ACLs, and other resources.
What you can do after
Operate/configure Kafka resources through Git-backed Kubernetes reconciliation and an operator.

Read how Kafka for Architects explains custom resource definition →

Logs and Telemetry

A custom resource definition is a Kubernetes API extension that defines a new custom resource type.

How it is used
Extends Kubernetes so Fluent Operator components can be deployed and configured through declarative resources.
How deep it goes
Defines several resource roles and shows selector-based configuration, but does not detail CRD schema authoring or controller internals.
Examples
Uses FluentBit, ClusterFluentBitConfig, and FluentBitConfig resources with enabled-label selectors for logging inputs, filters, and outputs.
What you can do after
Operate Fluent Bit through Kubernetes resources that select and assemble logging components.

Read how Logs and Telemetry explains custom resource definition →

Also covered in

What to know first

Related concepts

Questions about custom resource definition

What is custom resource definition?

A CustomResourceDefinition is a Kubernetes API object that defines a custom resource type and its schema.

Which Manning books explain custom resource definition?

Acing the Certified Kubernetes Administrator Exam, Second Edition, Server-Side WebAssembly, Kubernetes in Action, Second Edition, Designing Deep Learning Systems: A guide for software engineers, Kubernetes for Developers, Kargo in Action, Kafka for Architects and Logs and Telemetry.

What should I know before learning custom resource definition?

Manning books that teach custom resource definition usually introduce GitOps, YAML, load balancing and service discovery first.

What is custom resource definition a kind of?

Custom resource definition is a kind of extension interface. An extension interface is a defined integration point through which additional functionality can be added to Kubernetes without modifying its core codebase.

What is custom resource definition also called?

Custom resource definition is also called CRDs.

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.