Skip to content

Understanding the behavior of duration in scale up triggers #601

Closed Answered by mumoshu
Puneeth-n asked this question in Questions
Discussion options

You must be logged in to vote

@Puneeth-n It should be scale-down after 90m since the addition of the capacity.

What's in your HRA.Spec.CapacityReservations? Try running kubectl get on it to see. Each scale-up trigger results in adding an entry under that, and only "unexpired" capacity reservations count into the final desired replicas number.

Replies: 4 comments 4 replies

Comment options

You must be logged in to vote
1 reply
@Puneeth-n
Comment options

Comment options

You must be logged in to vote
3 replies
@Puneeth-n
Comment options

@mumoshu
Comment options

@Puneeth-n
Comment options

Answer selected by mumoshu
Comment options

You must be logged in to vote
0 replies
Comment options

You must be logged in to vote
0 replies
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested RunnerDeployment Discussions around RunnerDeployment Kubernetes Autoscale
4 participants