Skip to content

Having programable, the waiting time before the "autoscale-up/down" is effective #56335

@rsd35410

Description

@rsd35410

Is this a BUG REPORT or FEATURE REQUEST?:

Kind feature
@kubernetes/sig-autoscaling-feature-requests
@kubernetes/sig/autoscaling

What happened:

There is no way to change the waiting time before the "autoscale-up/down" is effective.
In addition, when the "autoscale-up" is performed, it is not directly scaled to the max number defined inside the HPA.

What you expected to happen:

Having these parameters configurable into the template definition of the HPA, like:

  • "scale-up" waiting time
  • "scale-down" waiting time
  • "scale-up" step
  • "scale-down" step

How to reproduce it (as minimally and precisely as possible):

Anything else we need to know?:

Environment:

  • Kubernetes version (use kubectl version):
  • Cloud provider or hardware configuration:
  • OS (e.g. from /etc/os-release):
  • Kernel (e.g. uname -a):
  • Install tools:
  • Others:

Metadata

Metadata

Assignees

No one assigned

    Labels

    kind/featureCategorizes issue or PR as related to a new feature.lifecycle/rottenDenotes an issue or PR that has aged beyond stale and will be auto-closed.sig/autoscalingCategorizes an issue or PR as relevant to SIG Autoscaling.

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions