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 ):
Now go ahead, create your first custom resource, and extend your cluster’s API with confidence. g/co/crd/setup
apiVersion: apiextensions.k8s.io/v1 kind: CustomResourceDefinition metadata: name: databasebackups.stable.example.com spec: group: stable.example.com versions: - name: v1 served: true storage: true schema: openAPIV3Schema: type: object properties: spec: type: object properties: backupSchedule: type: string retentionDays: type: integer scope: Namespaced names: plural: databasebackups singular: databasebackup kind: DatabaseBackup shortNames: - dbb Use kubectl to apply your CRD: 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. Conclusion Setting up a CRD — following the