Background

When new API versions are introduced to CRDs during an upgrade, it's important that:
The storage version remains the previous version (not the new one) until data migration is complete
Both old and new versions are served to maintain compatibility
This test helps catch potential issues where a new API version is immediately set as the storage version, which could cause problems with existing data stored in etcd.

What's required

Validation Checks

A test defines the following checks:

[sig-api-machinery] CRDs with new API versions should not change storage version immediately
Fails if a CRD has a new version added AND that version immediately becomes the storage version
This check ensures safe API version introduction practices

Summary Generation

a JSON summary file (crd-version-summary.json) to storage for inspection
Computes differences between before/after snapshots:
Added CRDs
Removed CRDs
Changed CRDs (with details on added/removed versions and storage changes)

Steps

• create a PR in origin

Stakeholders

• TRT
• All OpenShift teams

Definition of Done

• PR merged in origin
• Sending out email to aos-devel

• Docs

• <Add docs requirements for this card>

• Testing

• <Explain testing that will be added>