Skip to content
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

how does the cluster autoscaler move pods? #1776

Closed
nhooyr opened this Issue Mar 11, 2019 · 3 comments

Comments

Projects
None yet
3 participants
@nhooyr
Copy link

nhooyr commented Mar 11, 2019

Does it start the new pod first and then shutdown the old one?

Or shutdown the old one and then start the new one?

Would be good for the FAQ.

@nhooyr

This comment has been minimized.

Copy link
Author

nhooyr commented Mar 11, 2019

Reason I ask is if its the second, then I cannot ensure that at least one replica is active because maybe all my deployment's pods are on a single node. Whereas with the first I can.

@lsytj0413

This comment has been minimized.

Copy link
Contributor

lsytj0413 commented Mar 11, 2019

when CA decide to remove one node, it will evict all the pod on the node first, and it won't care about whether the pod is running on another node.

Note CA won't remove a node if there is a independent pod is running.

@aleksandra-malinowska

This comment has been minimized.

Copy link
Contributor

aleksandra-malinowska commented Mar 11, 2019

You can set PodDisruptionBudget for your workload. With maxUnavailable: 1 (or an equivalent configuration using minAvailable), pods should be evicted one after another.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.
You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session.