-
### Report
We install the Keda helm chart in another namespace (called keda) and in the last versions of helm chart we receive this errors in the pod `keda-operator-metrics-apiserver`
`1 requesthe…
-
### Report
Encountered one panic:
```
panic: runtime error: index out of range [1] with length 0
goroutine 1738630 [running]:
github.com/kedacore/keda/v2/pkg/scaling/cache.(*ScalersCache).ref…
-
### Report
When applying a ScaledObject which has both fallback set and is also using a CPU (or Memory?) trigger, the admission webhook emits a validation error but the update still gets applied to t…
vzdai updated
2 weeks ago
-
**Describe the solution you'd like**
it would be great to support use of workload identity (With a managed identity) in KEDA in order to handle the secrets that is used by trigger
IE guide form k…
-
**Problem**
Currently, users can configure KEDA scaling options through annotations when creating a KafkaSource. We should support the same set of annotations on triggers.
**[Persona:](https:/…
-
### Report
We are running the Generative AI workloads (GPU resources) using Keda-scaled jobs. We are not able to achieve streaming of Keda-scaled jobs.
### Expected Behavior
**Scenarios:**
…
-
### Proposal
When I deployed keda components using helm chart, I scanned relevant components by mirroring keda, keda-metrics-server and keda-admission-webhooks (using Trivy@v0.29.2). Security risks…
-
### Use-Case: ☂ Umbrella issue
This is a checklist for the [CNCF technical documentation analysis and implementation plan](https://github.com/cncf/techdocs/pull/215). It should be updated as sub-is…
-
Hi there,
We are currently using the Keda chart `v2.13.2` and everything works perfectly. After we upgraded to `v2.14.2` we are getting the following error in the component `Keda-operator`:
```
E…
-
**What happened**:
This is part of our kubestate customresource configuration:
```
- errorLogV: 0
groupVersionKind:
group: operator.kyma-project.io
ki…