You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Mar 9, 2021. It is now read-only.
A developer may set some autoscaling configs like --limits-cpu or --limits-memory as what kn service create described today. However, a Knative administrator may need to update some overall configs like stable-window or panic-window-percentage or ticker-interval for the whole Knative platform. The kn-admin will list all the config we support to update by kn-admin
According the Knative 0.16 doc about autoscaling, plan support following global configs to help with admin work. (Per-revision config is not planned here, that are more for developer experience)
$ kn admin autoscaling update
- Stable-window xx
- panic-window-percentage xx
- max-scale-up-rate xx
- container-concurrency-target-default xx
- container-concurrency-target-percentage xx
- requests-per-second-target-default xx
If there're any other autoscale configs that should be controlled by Knative administrator, please feel free to leave a comment in this issue. Thanks!
A developer may set some autoscaling configs like
--limits-cpuor--limits-memoryas what kn service create described today. However, a Knative administrator may need to update some overall configs likestable-windoworpanic-window-percentageorticker-intervalfor the whole Knative platform. The kn-admin will list all the config we support to update by kn-adminAccording the Knative 0.16 doc about autoscaling, plan support following global configs to help with admin work. (Per-revision config is not planned here, that are more for developer experience)
If there're any other autoscale configs that should be controlled by Knative administrator, please feel free to leave a comment in this issue. Thanks!