-
### Proposal
I am using the same setup as @chrismilson posted on https://github.com/kedacore/keda/issues/5451. However, I want to override the `identityId` (Azure UMI `clientId`) without hardcoding i…
-
Just disable prometheus-adapter and use metrics-server instead. They serve the same purpose, since AKS already provides metrics-server by default, don't use prometheus adapter.
_Origi…
-
### Report
When I install a Helm chart containing both an external scaler GRPC service and a `ScaledObject`, the resulting HPA has an **empty list of metrics** (K8s inserts the default 80% CPU util…
-
Support workload expansion on multiple clusters
### Use-Case
HTTP/gRPC based workloads have first class support for multi-cluster expansion by several multi-cluster ingress controllers.
But queue w…
-
### Report
When attempting to use Keda's ScaledObject to scale deployments based on RabbitMQ messages, scaling works as expected with classic queues but fails when using quorum queues.
### Expected …
-
As @zroubalik pointed out, we can propose to introduce a new character in the Phippy and Friends family that represents KEDA.
This issue is to brainstorm names and animals after which we can cast a…
-
### Report
After upgrading to version 2.12.0, you need to recreate the TriggerAuthentication resource (if you are using PodIdentityProviderAzure \ PodIdentityProviderAzureWorkload with an unspecified…
-
### Proposal
**Feature request:**
Ability to configure the targetPort of the interceptor-proxy service to have it listen on port 80
**Workarounds:**
1) Set the interceptor.proxy.port to 80 and …
-
### Report
- 0-4 HTTPScaledObject with targetPendingRequests = 40
- send 10 requests, scales up to 1, everything works
- send 150 requests, _all 150 requests go to the single replica while the othe…
-
### What happened?
When we enable autoscaling in helm chart, It doesn't work properly.
I'm using selenium grid helm chart on EKS. It works without autoscaling enabled But when I enable autoscaling,…