-
Notifications
You must be signed in to change notification settings - Fork 693
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Move CRDs to v1beta1 for 1.0.0-beta1 #1140
Comments
Are there any pointers on where to start? and what is the outcome, I would like to check this. But no idea where to start |
@mario-mazo thanks for your interest! |
How is this going? Is it still up for grabs? I'd like to take a look at it |
I think it's wise to do this after the merge of #1723, because it affects a lot of files. |
Two issues we have to consider here: Do we need a minimal form of backwards compatibility?What I mean by that: should it be possible for people running a previous version of ECK to install 1.0.0-beta1 into an existing cluster? If the answer is to that question is yes then we have to ship both API versions (
If the answer to "Do we need minimal backwards compatibility?" is no we should be aware of the consequences:
Finally there is the question how will we retire
|
Regarding the
|
Considering the (breaking) API revisions we have made and given that we want to express the beta level maturity of our CRDs we should move our resources to v1beta1 for
0.9.01.0.0-beta1.The text was updated successfully, but these errors were encountered: