-
Notifications
You must be signed in to change notification settings - Fork 1
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
amend UVIP KEP with some additional details #20
Conversation
keps/sig-api-machinery/3903-unknown-version-interoperability-proxy/README.md
Outdated
Show resolved
Hide resolved
keps/sig-api-machinery/3903-unknown-version-interoperability-proxy/README.md
Outdated
Show resolved
Hide resolved
requests reflect the newest one. We specifically rule out merging discovery docs, because | ||
merging discovery is: | ||
|
||
* complicated |
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.
this part still seems wrong to me or at least needs to go in an unresolved block
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.
Sure moved.
locally (we can use the StorageVersion API), it will proxy the request to | ||
one of the apiservers that is listed in the object. If an apiserver fails | ||
to respond is not available, then we will return a 503 (there is a small | ||
possibility of a race between the controller registering the apiserver |
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.
I'm gonna merge this but we need a better story for this race, IMO
No description provided.