Validated rendered manifests against Kubernetes 1.31 schemas plus JSON schemas I generated from the vendored CRDs. It caught a missing required field in a pod failure policy.
- What worked
- Strict mode with custom schema locations caught real errors.
- What got in the way
- CRD validation needs you to convert schemas into its file-naming convention yourself.