Let KEDA functions scale to zero#3925
Conversation
|
|
|
Welcome @Tushar-Khandelwal-2004! It looks like this is your first PR to knative/func 🎉 |
|
Hi @Tushar-Khandelwal-2004. Thanks for your PR. I'm waiting for a knative member to verify that this patch is reasonable to test. If it is, they should reply with Regular contributors should join the org to skip this step. Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. DetailsInstructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: Tushar-Khandelwal-2004 The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
Title: Let KEDA functions scale to zero by default
Why
The KEDA deployer currently defaults
minReplicaCountto1when generating theHTTPScaledObject. That keeps at least one function pod running even when there is no traffic, so functions cannot scale to zero by default.KEDA's HTTP add-on supports waking the function back up through the interceptor, and users who want to avoid cold-start latency can still set
scale.min: 1explicitly.Fixes #3924.
What changed
replicas.minvalue to0.deploy.options.scale.minvalue.Testing
go test -count=1 ./pkg/keda