-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
KCP: ensure machine that is being deleted during upgrades or scale down isn't the etcd leader #2398
Comments
@randomvariable: Please ensure the request meets the requirements listed here. If this request no longer meets these requirements, the label can be removed In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
I would argue that we should probably always handle this by moving the leadership, otherwise we risk causing conflicts with the failure domain handling. |
In terms of milestone, when do we want to tackle this? |
I think we still want to attempt to get this in prior to v0.3.0. |
/priority important-soon |
/assign @alexander-demichev |
Are we planning to do this for |
let's leave it in v0.3.0 and if it looks like it will merge today i'll put it in the RC milestone |
We need to update the first comment or title to reflect that this is specifically about upgrades. |
/retitle KCP: ensure machine that is being deleted during upgrades isn't the etcd leader |
/milestone v0.3.x |
Detailed Description
For correctness, the control plane controller should ensure etcd leadership is on a machine that isn't about to be deleted. Two optimisations are possible:
/kind feature
/help
The text was updated successfully, but these errors were encountered: