Handle API lifecycle, add support for APIConversions#61
Conversation
|
Skipping CI for Draft Pull Request. |
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
|
/test all |
On-behalf-of: @SAP christoph.mewes@sap.com
On-behalf-of: @SAP christoph.mewes@sap.com
Since a CRD has a _list_ of versions, there is no risk of running into map collisions when renaming versions, so we can slim down our API to just a map, no individual steps. On-behalf-of: @SAP christoph.mewes@sap.com
…ion object in kcp On-behalf-of: @SAP christoph.mewes@sap.com
|
/test all |
On-behalf-of: @SAP christoph.mewes@sap.com
|
/test all |
|
@xrstf: The following test failed, say
DetailsInstructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here. |
|
Superseded by #62, which is the same as this but without all the APIConversion stuff. |
Summary
What Type of PR Is This?
/kind feature
Related Issue(s)
Fixes #12
Release Notes