-
Notifications
You must be signed in to change notification settings - Fork 4.7k
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
kops rolling-update should do a real rolling-update #37
Comments
We should also evict nodes before terminating them. |
What about using a similar strategy to that followed by pod rolling updates in kubernetes?
I am not an expert on how ASGs work on EC2 but doing this naively may have some problems, namely that it could be slow to wait for the ASG to realize that |
Note: we should also rolling-update the masters before the nodes, in the case of an version upgrade. |
This is handled much better in my open PR. |
@chrislovecnm - pointer please? Which PR? |
#1134 Drain and validate in rolling update |
Is this is expected in 1.5.1? |
@mirague I am working on the PR again today, hopefully, our next release with a feature flag to turn it on. |
That's fantastic to hear, thanks @chrislovecnm ! |
any update on this? |
@chrislovecnm any updates here ? |
@Miyurz we have had a feature flag in that allows for drain and validate. It is stable, especially for stateless applications. We need some more TLC for stateless applications. Use KOPS_FEATURE_FLAGS="+DrainAndValidateRollingUpdate" to use beta code that drains the nodes and validates the cluster. New flags for Drain and Validation operations will be shown when |
Closing is this is stable, and we have #1718 |
…re/nba_full to develop * commit '0c6bd01682f69a91c55fb14cd872c83accc8c299': Refactor live job to abstract class and implementations
Right now it is a hacky timing-based loop.
Ideally we would wait for the new node to be registered.
The text was updated successfully, but these errors were encountered: