Skip to content

Relative maxSize on autoscaling pools #5

@coryodaniel

Description

@coryodaniel

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.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions