k8s-crd-design-review

To review a Kubernetes CRD for safe API design, validate schema invariants, status conventions, and reference patterns. Apply cross-field CEL rules, subresource usage, and GitOps compatibility checks to ensure a strict, evolvable API contract aligned with Kubernetes conventions.

The best way to validate cross-field rules in Kubernetes CRDs is by applying CEL validations. This enforces schema invariants and safe API semantics directly within the CRD, ensuring robust constraints without relying solely on external webhooks.

GitOps compatibility requires strict separation of spec and status subresources in Kubernetes CRDs. Designing status conventions with conditions and observedGeneration improves operator observability and prevents automated reconcilers from overwriting desired state.

You need webhooks for Kubernetes CRD validation when logic exceeds CEL expression capabilities or requires external data lookups. Use focused webhooks for complex admission control, while relying on CEL for structural schema invariants and standard field constraints.

To plan versioning and migration in Kubernetes CRDs, audit API semantics and structural schemas to identify breaking changes. Generate a formal compatibility assessment and actionable change recommendations to facilitate safe API evolution across versions.

Yes, you can audit operator observability through Kubernetes CRD printer-columns. Defining appropriate printer-columns alongside status conditions and observedGeneration enhances CLI visibility and improves operational readiness for cluster operators.