The scaledown:nodedeletion metric duration was incorrectly being computed relative to the start of the RunOnce routine, instead of from the actual start of the deletion. Behavior in the start of the routine (like a long cloudproviderrefresh) would incorrectly skew the nodedeletion duration Signed-off-by: Domenic Bozzuto <dom.bozzuto@datadoghq.com> |
||
|---|---|---|
| .. | ||
| currently_drained_nodes.go | ||
| currently_drained_nodes_test.go | ||
| filter_out_daemon_sets.go | ||
| filter_out_daemon_sets_test.go | ||
| filter_out_schedulable.go | ||
| filter_out_schedulable_test.go | ||
| pod_list_processor.go | ||