-
Notifications
You must be signed in to change notification settings - Fork 42k
Cloning v1beta3 as v1 and exposing it in the apiserver #7454
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
Conversation
|
cc @bgrant0607 |
hack/local-up-cluster.sh
Outdated
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We shouldn't enable v1 by default.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Reverted
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why do we need all these conversions? I'd expect the internal rep to be very close to the v1 API.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It's an optimization that @wojtek-t is working on. They're auto-generated.
|
Looks OK, unfortunate that everything has to be done in four places now... |
|
Hopefully we can get rid of v1beta1/2 in a couple weeks, which should help a lot. |
|
LGTM. Will merge on green. We can fix anything necessary, like removing minions, in subsequent, smaller PRs. |
|
Both travis and shippable are very backed up, so it may be a while. |
|
Yes. Right now, this is just an "as-is" copy of v1beta3. |
|
Shippable is green!! |
Cloning v1beta3 as v1 and exposing it in the apiserver
For #7018