In what area(s)?
/area autoscale
Expected Behavior
When minScale is specified for routable revisions KPA never scaled to below minScale.
Actual Behavior
When a revision is just created with minScale (e.g. 5) there's a small gap between revision becoming ready and route shift, which means that a ready revision is not routable for short period of time. But it is enough for AS to scale down.
Steps to Reproduce the Problem
- Create RunLatest minScale=5
- Create another revision with same minScale
- Observe (mostly via logs, but sometimes visible via kubectl) that we scale down to 0-2 (depending on traffic) and then back up to 5.
/cc @mattmoor @markusthoemmes @tanzeeb
In what area(s)?
/area autoscale
Expected Behavior
When minScale is specified for routable revisions KPA never scaled to below minScale.
Actual Behavior
When a revision is just created with minScale (e.g. 5) there's a small gap between revision becoming ready and route shift, which means that a ready revision is not routable for short period of time. But it is enough for AS to scale down.
Steps to Reproduce the Problem
/cc @mattmoor @markusthoemmes @tanzeeb