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.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
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.
The text was updated successfully, but these errors were encountered:
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 runningWe 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 thekops rolling-update
commands manually, but it would be great to avoid any manual kops commands if possible.The text was updated successfully, but these errors were encountered: