5 ms·
Constantly rotating nodes in and out of the cluster and restarting/relocating pods, even if mostly automated, causes a lot of needless infrastructure strain. It
by paxys 6y ago
Constantly rotating nodes in and out of the cluster and restarting/relocating pods, even if mostly automated, causes a lot of needless infrastructure strain. It is IMO one of the most overlooked parts of Kubernetes, and I wish there was a better solution to maintain stable, long-running processes when needed.
- dharmab 6y agoIf your pods need to be long running, you can annotate them as such and they will not be autoscaled. https://github.com/kubernetes/autoscaler/blob/master/cluster-autoscaler/FAQ.md#what-types-of-pods-can-prevent-ca-from-removing-a-node https://github.com/kubernetes/autoscaler/blob/master/cluster...
- ComputerGuru 6y agoWill they then also not be updated?
- dharmab 6y agoNot automatically. The autoscaler and other tooling will wait for the Pod to complete execution, or you can manually force the upgrade.