epic: API evolution #4344

Demo Objective

Service owners are able to evolve their APIResouceSchema-based APIs.

Find out & fill in the missing blanks in the code base, provide e2e tests and add docs.

Consider APIConversion.apis.kcp.io as well as conversion-webhook scenarios.

Demo Steps

1. Service owner creates APIResourceSchema & APIExport for v1alpha1 of the API.
2. Service consumer binds to the APIExport, observes v1alpha.
3. Service owner updates the APIExport with v1alpha2 of the schema; both v1alpha1 and v1alpha2 are served.
4. Service consumer is able to use v1alpha1 and v1alpha2.

Stretch goals:
5. (assume all clients have switched to v1alpha2) Service owner deletes v1alpha1.
6. Service consumer is able to use v1alpha2. v1alpha1 does not exist anymore.

Action Items

• Scope of the current demo is necessary to fit in the prototype boundaries
• Contribute to the final demo script and recording

Stories

No response