FAQ Latest
What is KEDA and why is it useful?
What are the prerequisites for using KEDA?
Does KEDA depend on any Azure service?
Does KEDA only work with Azure Functions?
Why should we use KEDA if we are already using Azure Functions in Azure?
- Run functions on-premises (potentially in something like an ‘intelligent edge’ architecture)
- Run functions alongside other Kubernetes apps (maybe in a restricted network, app mesh, custom environment, etc.)
- Run functions outside of Azure (no vendor lock-in)
- Specific need for more control (GPU enabled compute clusters, policies, etc.)
Can I scale my HTTP container or function with KEDA and Kubernetes?
KEDA will scale a container using metrics from a scaler, but unfortunately there is no scaler today for HTTP workloads.
We recommend using the Prometheus scaler to create scale rule based on metrics around HTTP events for now. Read Anirudh Garg’s blog post to learn more.
Where can I get to the code for the Scalers?
Is short polling intervals a problem?
How can I get involved?
- Pick up an issue to work on. A good place to start might be issues which are marked as Good First Issue or Help Wanted
- We are always looking to add more scalers.
- We are always looking for more samples, documentation, etc.
- Please join us in our weekly standup.
Can KEDA be used in production?
What does it cost?
How do I access KEDA resources using client-go
?
How do I run KEDA with readOnlyRootFilesystem=true
?
By default you can’t run KEDA with readOnlyRootFilesystem=true
because Metrics adapter generates self-signed certificates during deployment and stores them on the root file system.
To overcome this, you can create a secret/configmap with a valid CA, cert and key and then mount it to the Metrics Deployment.
To use your certificate, you need to reference it in the container args
section, e.g.:
args:
- '--client-ca-file=/cabundle/service-ca.crt'
- '--tls-cert-file=/certs/tls.crt'
- '--tls-private-key-file=/certs/tls.key'