Open linki opened 7 years ago
A fix would reduce the number of creating and terminating skipper
s for ingress in our setup which would be a way to reduce the occurrences of https://github.bus.zalan.do/teapot/issues/issues/568.
This is a duplicate of #1.
A cool off period as described in #28 could mitigate the observed behavior.
The autoscaler is great. However it can get into a state where it switches the desired node count back and forth due to small increase and decrease of workload in the cluster.
Let's assume cluster autoscaler inspects all pods and calculates a desired capacity of 12 nodes. Now let's assume a cron job spins up a pod every 5 minutes which would just be enough to have autoscaler calculate a desired node count of 13 nodes.
In that case autoscaler would constantly switch between 12 and 13 desired nodes because it sometimes inspects the cluster while the cron job is running and sometimes while it's not.
This could be the reason for the following behaviour:
However, since not strictly wrong, a constantly flipping node count seems unnecessary and could trigger superflous pod restarts of client applications.