Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Changes
This adds an empty v1alpha2 package, which serve as the base to port
v1alpha1 types to v1alpha2 while still being able to work on
v1alpha1 and do the appropriate refactoring while doing this.
Signed-off-by: Vincent Demeester [email protected]
This is the smallest change from #1529 I could came up with to "bootstrap" my work without having to go through rebase and refactoring hell in one go 😅
The package name doesn't really matter and could be renamed
v1beta1
later on. It is not exposed/published or even taken into account by anything (webhook, controller, …), except that client are generated. Which leads to a question : should we have the clients generated now or in the "latest" piece of dev on this ?This should allow us working on this quickly without fear of breaking people and without having to get it in for 0.9.0 👼
/cc @bobcatfish @skaegi @dlorenc @imjasonh
Submitter Checklist
These are the criteria that every PR should meet, please check them off as you
review them:
See the contribution guide for more details.
Double check this list of stuff that's easy to miss:
cmd
dir, please updatethe release Task to build and release this image.
Reviewer Notes
If API changes are included, additive changes must be approved by at least two OWNERS and backwards incompatible changes must be approved by more than 50% of the OWNERS, and they must first be added in a backwards compatible way.