README 未给出具体命令,部署方式(Helm、Operator Hub、YAML)需查阅官方部署文档

keda
kedacoreApache-2.0活跃维护基于 Kubernetes 的事件驱动自动伸缩组件,能根据队列、消息等事件源动态扩缩容任意容器,让无服务器和事件驱动负载按需伸缩。
KEDA is a Kubernetes-based Event Driven Autoscaling component. It provides event driven scale for any container running in Kubernetes
README 未给出具体安装命令,仅指向部署文档:https://keda.sh/docs/latest/deploy/README 未说明
KEDA 是 Kubernetes 上的事件驱动自动扩缩容组件,支持按事件源精细伸缩,包括缩容到零
基于 Kubernetes 的事件驱动自动伸缩组件,能根据队列、消息等事件源动态扩缩容任意容器,让无服务器和事件驱动负载按需伸缩。
核心能力
- 作为 Kubernetes Metrics Server 提供指标
- 用自定义资源定义声明扩缩容规则
- 与 Horizontal Pod Autoscaler 原生集成
- 支持缩容到零及从零扩容
- 无外部依赖,可跑在云和边缘
容易踩的坑
- v2.21.0最新正式版2026-09-23 · 2026-09-23 16:20 UTC
We are happy to release KEDA 2.21.0 🎉
[!IMPORTANT] KEDA 2.21.0 contains three breaking changes. If you are upgrading from KEDA 2.20, review Upgrading from KEDA 2.20 to 2.21 before upgrading.
Before upgrading from KEDA 2.20
Service account token audience enforcement (CVE-2026-77524)
KEDA 2.21 fixes the critical CVE-2026-77524 / GHSA-637c-6jxx-4rwm. You are affected if you use:
- Vault Kubernetes authentication, including configurations using the operator token, an existing projected token, or
credential.serviceAccountName. - Any
TriggerAuthenticationorClusterTriggerAuthenticationusingboundServiceAccountToken, including integrations with Metrics API, Prometheus, Loki, Datadog Cluster Agent, and other token-authenticated receivers.
You are not affected if you use ordinary Vault token authentication, API keys, OAuth credentials, or another authentication method that does not use a bound service account token. Before upgrading, review carefully the upgrade guide
Temporal Rules-Based Versioning settings
The Temporal scaler no longer accepts the deprecated
buildId,selectAllActive, andselectUnversionedsettings. Existing ScaledObjects and ScaledJobs containing them will fail scaler metadata parsing. Remove the settings for unversioned workers, or migrate versioned workers toworkerDeploymentNameandworkerDeploymentBuildId. See Temporal Rules-Based Versioning settings.Azure Pipelines in-flight jobs
KEDA 2.21 adds scaleOnInFlight, defaulting to true. Queue length now includes unfinished jobs already assigned to an agent. Set scaleOnInFlight: false to retain the unassigned-only behavior from KEDA 2.20; for ScaledJobs, combine this with the accurate scaling strategy. See Azure Pipelines in-flight jobs.
Highlights
- Reduce redundant scaler-backend requests when the HPA already owns the scaling decision (#7999, #8031).
- Add Azure Cosmos DB Change Feed, ClickHouse, and GCP Cloud Spanner scalers.
- Let external scalers update HPA targets dynamically through
StreamMetricSpec, and expose external-scaler gRPC client metrics. - Add Prometheus OAuth2 client-credentials authentication, Kafka Kerberos credential-cache support, and Azure Pipelines service-principal authentication.
- Improve scaler and authentication lifecycles with deterministic cancellation, refresh handling, Kubernetes API timeouts, and external-scaler connection cleanup.
Deprecation notice
The Liiklus scaler is deprecated because the upstream project is unmaintained. Its code is planned for removal in a later KEDA release. See #7929.
Learn how to deploy KEDA by reading our documentation.
🗓️ The next KEDA release is currently estimated for the 2nd week of January 2027. Learn more in our roadmap.
Breaking Changes
1e21cc7: Security: Enforce explicit service account token audiences to prevent TriggerAuthentication privilege escalation (CVE-2026-77524 / GHSA-637c-6jxx-4rwm; migration guide) (@wozniakjan)587d3cd: **Azure Pipeli
- Vault Kubernetes authentication, including configurations using the operator token, an existing projected token, or
- v2.20.22026-07-31 · 2026-07-31 08:14 UTC
查看更新说明
Release KEDA v2.20.2 :rocket:
⚠️⚠️⚠️⚠️ ⚠️ Please read upgrade notes if you are upgrading from version < 2.20.0: https://github.com/kedacore/keda/releases/tag/v2.20.0 ⚠️⚠️⚠️⚠️⚠️
Improvements
- General: Introduce a dedicated
HPAActivecondition onScaledObjectmirroring the HPA's ownScalingActivestatus, so transient HPA metric gaps no longer flip theReadycondition toFalse(#7914)
Fixes
- General: Fix concurrent map writes panic in the shared root CA
CertPool(#7910) - General: Fix nil pointer dereference in AWS Secret Manager
TriggerAuthenticationwhenawsSecretManager.credentialsis omitted and noawsSecretManager.podIdentityis set (#7927) - General: Fix nil pointer dereference in
customScalingStrategy.GetEffectiveMaxScalewhencustomScalingQueueLengthDeductionis omitted; the optional field is now treated as zero deduction instead of panicking (#7798) - General: Fix nil pointer dereference in
GetCurrentReplicaswhen a Deployment/StatefulSet/ReplicaSet is returned from the informer cache with an undefaultedspec.replicas; a nil value is now treated as the Kubernetes default of 1 instead of panicking (#7863) - General: Fix
ScaledJobCRD validation to include "default" as a valid value forscalingStrategy.strategy(#7855) - General: Guard
GetCurrentReplicasagainst nilStatus.ScaleTargetGVKRto prevent operator panics under the cache race documented in (#4389) / (#4955) - General: Restore core
""API group in events RBAC so that client-go's event broadcaster can write legacy events (#7922) - General: Restore gRPC reconnect backoff in the metrics service client; an unset
BackoffinWithConnectParamsdisabled backoff and caused a zero-delay reconnect loop that flooded logs when keda-operator was unreachable (#7856) - General: Share HTTP transports across scalers to reuse connection pools and avoid re-dial storms at high ScaledObject counts (#7789)
- General: Treat negative external metric values as zero to prevent incorrect HPA scaling (#7880)
- Azure Blob Storage Scaler: Fix
globPatternnever matching when written in path-style with a leading/, since blob names never have one (#6492) - MongoDB Scaler: Disconnect the client when the initial
Pingfails so the background topology-monitoring connections opened bymongo.Connectare not leaked (#5612)
New Contributors
- @Goutham-Annem made their first contribution in https://github.com/kedacore/keda/pull/7858
- @simplyaduck made their first contribution in https://github.com/kedacore/keda/pull/7857
- @itxaiohanglover made their first contribution in https://github.com/kedacore/keda/pull/7871
- @orfeldman-evolinq made their first contribution in https://github.com/kedacore/keda/pull/7904
- @vishnu97770 made their first contribution in https://github.com/kedacore/keda/pull/7928
- @sobol-sudo made their first contribution in https://github.com/kedacore/keda/pull/7932
Full Changelog: https://github.com/kedacore/keda/compare/v2.20.1...v2.20.2
- General: Introduce a dedicated
- v2.20.12026-06-08 · 2026-06-08 17:55 UTC
查看更新说明
Release KEDA v2.20.1 :rocket:
⚠️⚠️⚠️⚠️ ⚠️ Please read upgrade notes if you are upgrading from version < 2.20.0: https://github.com/kedacore/keda/releases/tag/v2.20.0 ⚠️⚠️⚠️⚠️⚠️
Fixes
- General: Fix concurrent map read/write data race in fallback
updateStatusthat caused panics when multiple triggers were scaling simultaneously (#7838) - General: Fix
KEDAScalersStarted"Started scalers watch" event not being emitted for ScaledJobs because it shared an events.k8s.io aggregation key with the per-scaler "scaler is built" event (#7820)
New Contributors
- @jiyuchen-stripe made their first contribution in https://github.com/kedacore/keda/pull/7843
Full Changelog: https://github.com/kedacore/keda/compare/v2.20.0...v2.20.1
- General: Fix concurrent map read/write data race in fallback
- v2.20.02026-06-01 · 2026-06-01 14:46 UTC
查看更新说明
We are happy to release KEDA 2.20.0 🎉
⚠️ Upgrade note: events moved to
events.k8s.io(#7781)With the Kubernetes 0.35 dependency bump, KEDA now records Kubernetes events via the
events.k8s.ioAPI group instead of the legacy coreeventsresource. If you deploy KEDA with custom or restricted RBAC, grant the operatorcreate/patchonevents.k8s.io/eventsbefore upgrading, otherwise event recording will fail. The bundled KEDA manifests and Helm chart already include the updated permissions.Highlights:
- Introduce new OpenSearch Scaler
- Introduce Elastic Forecast Scaler
- Add
scalingModifiersfallback behavior - Add support for AWS External ID in TriggerAuthentication podIdentity for all AWS scalers
- Add scaler HTTP request metrics for outbound requests made during metric collection
Learn how to deploy KEDA by reading our documentation.
🗓️ The next KEDA release is currently being estimated for 2nd week of September 2026, learn more in our roadmap.
New
- General: Add
scalingModifiersfallback behavior (#7366) - General: Introduce Elastic Forecast Scaler (#7494)
- General: Introduce new OpenSearch Scaler (#7456)
Improvements
- General: Add cooldownPeriod and pollingInterval checks for ScaledObject (#7271)
- General: Add CRD-level validation markers (Minimum, MinLength, MinItems, Enum) for ScaledObject, ScaledJob, ScaleTriggers, and TriggerAuthentication API types (#7533)
- General: Add
--leader-election-idflag to allow configuring the leader election Lease name (#7564) - General: Add scaler HTTP request metrics (
keda_scaler_http_requests_total,keda_scaler_http_request_duration_seconds) for outbound HTTP requests made during scaler metric collection (#6600) - General: Allow more control of TLS versions & ciphers via
KEDA_HTTP_TLS_CIPHER_LIST,KEDA_SERVICE_TLS_CIPHER_LISTandKEDA_SERVICE_MIN_TLS_VERSIONenv vars (#7617) - General: Cap each scalers-cache reader at a per-reader budget derived from
globalHTTPTimeoutsoScalersCache.Closecannot block indefinitely (#7574) - General: Make APIService cert injections optional (#7559)
- General: Remove unconditional
json.MarshalIndentcalls from admission webhook validation hot paths; replace spec-comparisonMarshalIndent-and-string-compare inisRemovingFinalizervariants withreflect.DeepEqual. Prevents webhook OOM under sustained admission load at large scale (observed at ~60k ScaledObjects) (#7670) - AWS Scalers: Add support for AWS External ID in TriggerAuthentication podIdentity for all AWS scalers (SQS, Kinesis, DynamoDB, CloudWatch, etc.) to enable cross-account access scenarios (#6921)
- Elasticsearch Scaler: Add HTTP status check for Elasticsearch errors (#7480)
- Github Runner Scaler: Handle rate limit errors by respecting X-RateLimit-Reset and Retry-After headers and returning cached queue length (#7683)
- Kubernetes Workload Scaler: Add
groupByNodeparameter (#7628) - Metrics API Scaler: Add custom HTTP client timeout ([#7549](https://
- v2.19.02026-02-02 · 2026-02-02 10:10 UTC
查看更新说明
We are happy to release KEDA 2.19.0 🎉
Highlights:
- Introducing new Kubernetes Resource Scaler
- Adding file-based authentication support for ClusterTriggerAuthentication
Learn how to deploy KEDA by reading our documentation.
🗓️ The next KEDA release is currently being estimated for 2nd week of May 2026 , learn more in our roadmap.
New
- General: Add file-based authentication support for ClusterTriggerAuthentication (#7083)
- General: Introduce new Kubernetes Resource Scaler (#7212)
Improvements
- General: Correct error message when awsSecretAccessKey is missing in credential-based authentication (#7265)
- General: Emit more events about what is happening with ScaledObject/ScaledJob (#7382)
- General: Raw metrics stream - include trigger activity status in response (#7369)
- AWS CloudWatch Scaler: Add cross-account observability support (#7189)
- Dynamodb Scaler: Add FilterExpression support (#7102)
- Dynatrace Scaler: Support DQL querying (#7377)
- MongoDB Scaler: Add TLS support (#6976)
Fixes
- General: Apply fallback in polling loop to enable scaling from zero (#7239)
- General: Fix accurateScalingStrategy ignoring pendingJobCount in maxReplicaCount check (#7329)
- General: Replace deprecated
azure autorestdependency toazure sdk for go(#7073) - Datadog Scaler: Return request in cluster agent proxy without bearer auth (#7341)
- Datadog Scaler: Use metricUnavailableValue for 422 errors in Datadog Cluster Agent (#7246)
- IBMMQ Scaler: Create new HTTP request for each queue query in IBMMQ scaler (#7202)
- Kafka Scaler: Improve check for missing partition information when calculating lag (#7414)
- Temporal Scaler: Fix TLS RootCAs initialization when using API key authentication with Temporal Cloud (#7367)
Breaking Changes
- NATS Streaming scaler: Remove NATS Streaming Server (aka Stan) (#6366)
Other
- ScaledObject/ScaledJob: Track activity for each trigger in the status (#7347)
用户点评
登录用户的真实使用记录,可按版本和硬件筛选还没有人点评。第一个说出真实体验的人最有价值。
KEDA allows for fine-grained autoscaling (including to/from zero) for event driven Kubernetes workloads. KEDA serves as a Kubernetes Metrics Server and allows users to define autoscaling rules using a dedicated Kubernetes custom resource definition.
KEDA can run on both the cloud and the edge, integrates natively with Kubernetes components such as the Horizontal Pod Autoscaler, and has no external dependencies.
We are a Cloud Native Computing Foundation (CNCF) graduated project.
Table of contents
- Getting started
- Documentation
- Community
- Adopters - Become a listed KEDA user!
- Governance & Policies
- Support
- Roadmap
- Releases
- Contributing
Getting started
- QuickStart - RabbitMQ and Go
- QuickStart - Azure Functions and Queues
- QuickStart - Azure Functions and Kafka on Openshift 4
- QuickStart - Azure Storage Queue with ScaledJob
You can find several samples for various event sources here.
Deploying KEDA
There are many ways to deploy KEDA including Helm, Operator Hub and YAML files.
Documentation
Interested to learn more? Head over to keda.sh.
Community
If interested in contributing or participating in the direction of KEDA, you can join our community meetings! Learn more about them on our website.
Just want to learn or chat about KEDA? Feel free to join the conversation in #KEDA on the Kubernetes Slack!
Adopters - Become a listed KEDA user!
We are always happy to list users who run KEDA in production, learn more about it here.
Governance & Policies
You can learn about the governance of KEDA here.
Support
Details on the KEDA support policy can found here.
Roadmap
We use GitHub issues to build our backlog, a complete overview of all open items and our planning.
Learn more about our roadmap here.
Releases
You can find the latest releases here.
Contributing
You can find contributing guide here.
Building & deploying locally
Learn how to build & deploy KEDA locally here.
Testing strategy
Learn more about our testing strategy here.