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

kops_cluster_updater rolling_update by instance-group/instance-group-roles #1113

Open
partcyborg opened this issue Mar 13, 2024 · 1 comment

Comments

@partcyborg
Copy link

Our kops clusters have a number of workloads that are sensitive to disruption so we try to avoid unplanned pod restarts. One of the ways that we do this is when we upgrade kops or kubernetes, we only perform kops rolling-update on the masters and specific node groups by running

$ kops update cluster --yes
$ kops rolling-update cluster --instance-group-roles Master --yes
$ kops rolling-update cluster --instance-group <safe pool a>,<safe pool b>... --yes

We then taint the nodes in the other pools and allow them to recycle naturally as workloads restart on their own.

Is there a way to implement an equivalent workflow using kops_cluster_updater? I know we can just disable rolling updates altogether and run the kops rolling-update commands manually, but it would be great to avoid any manual kops commands if possible.

@partcyborg
Copy link
Author

Since there does not appear to be support for this. I went ahead and sent out a PR adding it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
1 participant