-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
Update Efficient Watch Resumption KEP to Stable #3062
Update Efficient Watch Resumption KEP to Stable #3062
Conversation
- Rolling-upgrade of kube-apiservers in 5k-node cluster test is | ||
automated and running periodically. | ||
- Benefits of the feature during rolling upgrade of kube-apiserver at scale | ||
(thousands of nodes) proven in production |
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 still aren't testing HA clusters in upstream. Given that it will take more time (we're still trying to converge on what exact framework we should be using) and the fact that:
- we're somewhat-continuously testing it as prt of GKE
- we've already seen a proven effect/benefit from it on real production clusters
I don't want to block GA-ing this feature on that.
b26f07a
to
144ec1b
Compare
/approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: deads2k, wojtek-t The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
/lgtm |
Ref #1904
/sig api-machinery
/assign @deads2k @lavalamp