Goldpinger is too sensitive to autoscaler activity about goldpinger HOT 5 OPEN

Here's another case- a cluster had an autoscaler mass scale in event, which caused goldpinger to incorrectly report 23% of the network was failing.

from goldpinger.

Hello people!

We have the same issue ^^ but filtering out a node because of status NotReady is not correct as there are cases where node instead of being marked as NotReady because of scale-down, could be labeled NotReady as legitimately corrupted.

So we better focus on filtering out nodes on different label/attribute like SchedulingDisabled or smth. What do you think?

from goldpinger.

Hello!

Any updates on this one?

from goldpinger.

#107 should help - after the node eviction timeout, pods go to terminating state and goldpinger will stop trying to reach them

from goldpinger.

@rbtr thank you. I will give it a go and come back with some feedback in the next days.

from goldpinger.