How to categorize this issue?
/area auto-scaling
/area storage
/kind enhancement
What would you like to be added:
As proposed in GEP-0038, extend the API with a spec.volumePolicies[].scaleUp.cooldownDuration field which can be used to set the minimum time that must elapse after a scaling operation before another scaling operation can be triggered for the same PVC. This prevents rapid successive scaling operations and allows time for the system to stabilize after a resize. For example, 180s (3 minutes) ensures at least 3 minutes between resize operations.
Why is this needed:
This is needed when pvc-autoscaler runs on providers like AWS, that only allow changes to the persistent volumes only once every 6 hours.
How to categorize this issue?
/area auto-scaling
/area storage
/kind enhancement
What would you like to be added:
As proposed in GEP-0038, extend the API with a
spec.volumePolicies[].scaleUp.cooldownDurationfield which can be used to set the minimum time that must elapse after a scaling operation before another scaling operation can be triggered for the same PVC. This prevents rapid successive scaling operations and allows time for the system to stabilize after a resize. For example, 180s (3 minutes) ensures at least 3 minutes between resize operations.Why is this needed:
This is needed when
pvc-autoscalerruns on providers like AWS, that only allow changes to the persistent volumes only once every 6 hours.