G/co/crd/setup !link! -

Now go ahead, create your first custom resource, and extend your cluster’s API with confidence.

# Example: ./g/co/crd/setup.sh kubectl apply -f ./crds/ kubectl wait --for=condition=established --timeout=60s crd/databasebackups.stable.example.com echo "CRD setup complete." Check that your CRD was created successfully:

Double-check the schema section in your CRD — the structure must match exactly. g/co/crd/setup

kubectl apply -f my-resource-crd.yaml To follow the g/co/crd/setup pattern, you could wrap this in a script or Makefile:

kubectl apply -f my-backup.yaml List your custom resources: Now go ahead, create your first custom resource,

Mastering g/co/crd/setup: A Step-by-Step Guide to Custom Resource Definitions

apiVersion: stable.example.com/v1 kind: DatabaseBackup metadata: name: nightly-backup spec: backupSchedule: "0 2 * * *" retentionDays: 7 Apply it: They allow you to extend Kubernetes’ API and

April 14, 2026 Reading time: 5 minutes Introduction If you’ve been working with Kubernetes for a while, you’ve likely heard about Custom Resource Definitions (CRDs). They allow you to extend Kubernetes’ API and create your own resource types, just like pods or services.