kedacore/keda-olm-operator

Operator for deploying KEDA Controller on OperatorHub.io/OLM

Hosted by Cloud Native Computing Foundation · part of Linux Foundation

View on GitHub ↗Jump to charts ↓

kedacore/keda-olm-operator has 40+ stars and 30+ forks on GitHub, is written in Go, and was last pushed on Oct 14, 2026. Data as of . Signed-in members get hourly updates — create a free account.

Summary Information

Updated 1 hour ago
Type:Plugin / ExtensionCategory(s):Kubernetes & OperatorsCloud Native & Infrastructure
Added to GitGenius on October 15th, 2026
Created on December 11th, 2019
Open Issues & Pull Requests: 19 (+0)
GitHub issues: Enabled
Number of forks: 30
Total Stargazers: 41 (+0)
Total Subscribers: 5 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 43.6 days
Mean response time: 267.0 days
90th percentile: 772.3 days
Tracked items: 14

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 4
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 278 days
Stale 30+ days: 2
Stale 90+ days: 2

Recent activity

Opened in 7 days: 0
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 0

Top labels

  • bug (1)
  • good first issue (1)
  • help wanted (1)

Most active issues this week

Sign in to see which issues are moving.
Sign in

Detailed Description

KEDA OLM Operator is a Kubernetes operator that deploys the KEDA Controller through the Operator Lifecycle Manager framework on OpenShift or any OLM-enabled Kubernetes cluster.

The tool solves the problem of managing KEDA (Kubernetes Event-driven Autoscaling) deployments in environments that support OLM. It provides a KedaController custom resource that allows operators to configure and manage KEDA's behavior through Kubernetes-native declarative configuration. The operator handles deployment, configuration of environment variables, and integration with platform-specific features like GCP Workload Identity Federation. It also supports optional HTTP Add-on functionality with configurable behavior and status reporting.

Teams running Kubernetes or OpenShift clusters with OLM installed should choose this tool if they want to manage KEDA through the standard operator framework rather than manual installation. It suits organizations that prefer declarative, GitOps-friendly deployments and need to configure KEDA behavior at install time or through the KedaController resource. The tool supports both OperatorHub Marketplace installation and manual installation paths, giving flexibility in deployment approaches. Note that KEDA v1 and v2 cannot run on the same cluster, requiring uninstallation of v1 and its CRDs before adopting this operator.

The project maintains active continuous integration with both main build and nightly end-to-end test workflows. Development follows the Operator Framework patterns and includes local development support with documented prerequisites and build procedures for the operator image.