How to categorize this issue?
/area auto-scaling
/kind enhancement
/priority 2
What would you like to be added:
Currently, gardener users are required to adjust both the clusterAutoscaler.maxNodeProvisionTime and the machineControllerManager.machineCreationTimeout in the gardener shoot since the MCM does not honor the CA value. We want the MCM to honor the maxNodeProvisionTime if set by the gardener extension provider on the machine deployment via the autoscaler.gardener.cloud/max-node-provision-time annotation.
Why is this needed:
We want one single value to be adjusted on the shoot cluster and propagate to scaler (cluster-autoscaler) & lifecycle (machoine-controller). If CA is not running and the autoscaler.gardener.cloud/max-node-provision-time is not set, then the MCM falls back to the standard machineCreationTimeout
How to categorize this issue?
/area auto-scaling
/kind enhancement
/priority 2
What would you like to be added:
Currently, gardener users are required to adjust both the
clusterAutoscaler.maxNodeProvisionTimeand themachineControllerManager.machineCreationTimeoutin the gardener shoot since the MCM does not honor the CA value. We want the MCM to honor themaxNodeProvisionTimeif set by the gardener extension provider on the machine deployment via theautoscaler.gardener.cloud/max-node-provision-timeannotation.Why is this needed:
We want one single value to be adjusted on the shoot cluster and propagate to scaler (
cluster-autoscaler) & lifecycle (machoine-controller). If CA is not running and theautoscaler.gardener.cloud/max-node-provision-timeis not set, then the MCM falls back to the standardmachineCreationTimeout