Modify Kubernetes/OpenShift CRDs and API types with kubebuilder validation markers.
npx skills add https://github.com/wangke19/my-claude-skills --skill crd-update
Please help me install this Agent Skill. Skill: crd-update Source: https://github.com/wangke19/my-claude-skills/tree/main/plugins/ocp/skills/crd-update Command: npx skills add https://github.com/wangke19/my-claude-skills --skill crd-update
Safely updating Kubernetes/OpenShift CRDs and API types requires careful planning to preserve compatibility, manage API versioning, and avoid breaking changes. This skill provides a protocol for applying kubebuilder validation markers, regenerating manifests, and implementing migrations or conversion webhooks.
Follow the CRD update protocol to modify API types, regenerate manifests, and migrate changes safely.
High-intent search queries and answers about installing and using this skill.
To safely update Kubernetes CRDs, you modify API types with kubebuilder validation markers, regenerate manifests, and verify backward-compatibility. This process prevents breaking existing deployments by carefully managing field additions, removals, and version transitions.
You need a conversion webhook for backward-compatible API changes when altering CRD field types or structures across versions. It translates data between API versions, ensuring smooth upgrades and preserving compatibility when fields are modified in breaking ways.
The best way to add kubebuilder validation markers to CRD types is applying them directly to Go struct fields before regenerating manifests. This ensures the Kubernetes API server enforces schema validation rules, safeguarding CRD evolution.
Handling breaking API changes in OpenShift CRDs requires implementing versioned API types and conversion webhooks. You must establish clear migration paths, update API types, regenerate manifests, and integrate tests to manage the transition safely.
Yes, you need to regenerate manifests after modifying CRD API types. Regenerating manifests applies the updated kubebuilder validation markers and schema definitions to your Kubernetes manifests, ensuring the deployed CRDs match the new API type definitions.
Updating CRD types without conversion webhooks limits you to non-breaking changes like adding optional fields. Removing or renaming fields requires conversion webhooks to translate between API versions, preventing data loss and ensuring backward-compatibility.
missBergUpdate Envoy Gateway CRD Go types, validations, and code-generation scaffolding.
akin-ozerValidate Kubernetes YAML manifests for syntax and schema errors.
Veloxia-agencyBuild Kubernetes operators with controller-runtime or kubebuilder workflows.
missBergAutomate Kubernetes CRD design, validation, and lifecycle management with kubebuilder markers and CEL validation.
