What problem does it solve?
When migrating Config Connector resources from legacy to direct reconcilers, CRD schemas can accidentally drift, breaking existing user configurations. This Skill checks whether a modified CRD remains structurally equivalent or backward compatible with its previously committed version, catching breaking changes before they merge.
Core Features & Use Cases
- Equivalence Checking: Verifies that a changed CRD has no fields added or removed under spec and no type or CEL validation changes compared to a git reference like master.
- Backward Compatibility Checking: Confirms no fields were removed or renamed and no incompatible type changes were introduced, while allowing safe additions.
- Presubmit Integration: Used in CI presubmits such as dev/ci/presubmits/crd-equivalence-check to enforce KRM schema stability during reconciler migration.
- Use Case: Before promoting a CRD during a direct reconciler migration, run the equivalence check against master to confirm the schema was not unintentionally altered.
Quick Start
Ask the assistant to run the crd-mcp-server equivalence check on your modified CRD YAML file against the master git reference from the repository root.