Justyna Betkier b8db30c2fb Improve events when max total nodes of the cluster is reached. ... - log cluster wide event - previous event would never get fired because the estimators would already cap the options they generate and additionally it would fire once and events are kept only for some time - log per pod event explaining why the scale up is not triggered (previously it would either get no scale up because no matching group or it would not get an event at all) This required adding a list of pods that were unschedulable to the status in case when the max total nodes were reached.		2025-02-12 13:24:51 +01:00
..
autoscaling_status_processor.go	feat:add node group health and back off metrics	2024-01-23 19:39:18 +08:00
eventing_scale_up_processor.go	Improve events when max total nodes of the cluster is reached.	2025-02-12 13:24:51 +01:00
eventing_scale_up_processor_test.go	Improve events when max total nodes of the cluster is reached.	2025-02-12 13:24:51 +01:00
metrics_autoscaling_status_processor.go	feat:add node group health and back off metrics	2024-01-23 19:39:18 +08:00
scale_down_status_processor.go	Add ScaleDown.Actuator to AutoscalingContext	2022-11-02 13:12:25 +00:00
scale_up_status_processor.go	Improve logging when the cluster reaches max nodes total.	2025-01-29 13:37:48 +01:00