Update Scaled Node with extended resources from MachineClass NodeTemplate #955
Labels
area/auto-scaling
Auto-scaling (CA/HPA/VPA/HVPA, predominantly control plane, but also otherwise) related
kind/enhancement
Enhancement, improvement, extension
priority/3
Priority (lower number equals higher priority)
How to categorize this issue?
/area auto-scaling
/kind enhancement
/priority 3
What would you like to be added:
We have enhanced our CA fork to support extended resources for scale-from-zero. PR: gardener/autoscaler#334. However, scheduler cannot assign Pods to the scaled up Node unless the
Currently, stakeholders are manually using tools such as Kyverno policies to update the
Node
object with extended resources, but this is inconvenient and somewhat error prone due to possible divergence of the values in the CA Node Group and Kyverno policy. Since the MCM is the managing controller and already reads theMachineClass
it is best suited to update theNode
object with the extended resources specified in theMachineClass
Why is this needed:
Support for assigning Pods to Nodes scaled by CA belonging to NodeGroups declared with extended resources. Background covered at: gardener/autoscaler#132
The text was updated successfully, but these errors were encountered: