ballast
ballast copied to clipboard
Relative maxSize on autoscaling pools
Adding an additional option to relatively set the maxSize
Why
Since the minSize is being dynamically adjusted, when the source pool is under heavy load, the minSize of a target can potentially end up being larger than its maxSize which returns an error.
Its important to respect some form of "maximum" cost-wise, but in the event that workloads need to be served and there are no source nodes, it would be nice to be able to increase the max on a target pool so that work could be scheduled if the source pool was unschedule-able.
spec:
targets:
- name: foo
targetCapacityPercent: 30
relativeMaxSizePercent: 1000 # percent more than current minimum
Better YAML key name.