G/co/crd/setup 〈Confirmed »〉

kubectl get crd | grep databasebackups kubectl explain databasebackup You should see your new resource type available. Now that the CRD exists, create an instance of your custom resource ( my-backup.yaml ):

kubectl apply -f my-backup.yaml List your custom resources: 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 get crd | grep databasebackups kubectl explain

Use kubectl replace --force if needed, but prefer apply for declarative management. Conclusion Setting up a CRD — following the g/co/crd/setup approach — is straightforward once you understand the steps: define, apply, verify, and use. CRDs unlock the true extensibility of Kubernetes, letting you model your infrastructure exactly how your team needs it. CRDs unlock the true extensibility of Kubernetes, letting

Double-check the schema section in your CRD — the structure must match exactly.