KEDA is a Kubernetes-based Event Driven Autoscaling component. It provides event driven scale for any container running in Kubernetes
APACHE-2.0 License
Bot releases are hidden (Show)
Published by JorTurFer almost 3 years ago
We are happy to release KEDA 2.5.0 🎉
Here are some highlights:
subscriptionSize
is deprecated in favor of mode
and value
Learn how to deploy KEDA by reading our documentation.
MultipleScalersCalculation
(#2016)RolloutStrategy
(#2164)restAPITemplate
is given (#2104)SubscriptionSize
and OldestUnackedMessageAge
modes (#2266)unsafeSsl
parameter (#2157|#2320)metricName
(#2171)serverAddress
from generated metric name (#2099)queueName
and vhostName
before use them in query string (bug fix) (#2055)pageSize
(using regex) (#2162|#2319)unsafeSsl
parameter (#2157)MaxConcurrentReconciles
for controllers (#2272)ValueMetricType
using cpu_memory_scaler (#2218)IdleReplicaCount
are equal to MinReplicaCount
to be the same as the check (#2212)subscriptionSize
is deprecated in favor of mode
and value
(#2266)context.Context
values are properly passed down the stack (#2202|#2249)GetMetrics
call (#2255)github.com/kedacore/keda/v2/api/v1alpha1
-> github.com/kedacore/keda/v2/apis/keda/v1alpha1
Full Changelog: https://github.com/kedacore/keda/compare/v2.4.0...v2.5.0
queueName
and vhostName
in RabbitMQ Scaler before use them in query string (bug fix) by @JorTurFer in https://github.com/kedacore/keda/pull/2055
KEDA_HTTP_DEFAULT_TIMEOUT
by @JorTurFer in https://github.com/kedacore/keda/pull/2062
MultipleScalersCalculation
by @TsuyoshiUshio in https://github.com/kedacore/keda/pull/2016
dbName
property parsing by @JorTurFer in https://github.com/kedacore/keda/pull/2140
restAPITemplate
is given by @Ritikaa96 in https://github.com/kedacore/keda/pull/2104
unsafeSsl
parameter on InfluxDB by @dtsioumas in https://github.com/kedacore/keda/pull/2157
serverAddress
from generated metric name by @zroubalik in https://github.com/kedacore/keda/pull/2099
metricName
by @zroubalik in https://github.com/kedacore/keda/pull/2171
feature
as allowed label for stale issues, instead of feature-request
by @tomkerkhove in https://github.com/kedacore/keda/pull/2193
ValueMetricType
using cpu_memory_scaler by @JorTurFer in https://github.com/kedacore/keda/pull/2218
rolloutStrategy
by @etamarw in https://github.com/kedacore/keda/pull/2164
beta.kubernetes.io/os
nodeSelector is deprecated by @zroubalik in https://github.com/kedacore/keda/pull/2280
unsafeSsl
parameter in Selenium Grid scaler by @JorTurFer in https://github.com/kedacore/keda/pull/2285
pageSize
to avoid conversion problems by @zroubalik in https://github.com/kedacore/keda/pull/2319
MaxConcurrentReconciles
for reconcilers by @zroubalik in https://github.com/kedacore/keda/pull/2272
Published by tomkerkhove about 3 years ago
We are happy to release KEDA 2.4.0 🎉
Here are some highlights:
Learn how to deploy KEDA by reading our documentation.
authToken
, serverURL
, and organizationName
to be sourced from (Cluster)TriggerAuthentication
(#1904)kubectl get sj
(#1855)kubectl get ta
or kubectl get cta
(#1862)keda-system-auth-delegator
ClusterRoleBinding name (#1616). Upgrading may leave a stray ClusterRoleBinding with the old name keda:system:auth-delegator
behind.scaled[object/job].keda.sh/
prefix for KEDA related labels (#2008)Published by zroubalik over 3 years ago
We are happy to release KEDA 2.3.0 🎉
Here are some highlights:
Learn how to deploy KEDA by reading our documentation.
connectionString
parameter is added to metricName
due to uniqueness violation for clusters having more than one queue with the same name (#1755)allowIdleConsumers
to the list of trigger parameters (#1684)checkpointStrategy
to support more language-specific checkpoints (#1621)blobContainerName
and added a optional metricName
field (#1816)Published by zroubalik over 3 years ago
We are happy to release KEDA 2.2.0 🎉
Here are some highlights:
Learn how to deploy KEDA by reading our documentation.
publishRate
trigger to RabbitMQ scaler (#1653)KEDA_HTTP_DEFAULT_TIMEOUT
support in Operator (#1548)MIN field
for ScaledJob (#1553)swiftURL
parameter optional for the OpenStack Swift scaler (#1652)keda-metrics-apiserver
by setting a controller-runtime logger properly (#1654)Published by tomkerkhove over 3 years ago
We are happy to release KEDA v2.1.0 🎉
Here are some highlights:
ClusterTriggerAuthentication
for cluster-wide trigger authenticationLearn how to deploy KEDA by reading our documentation.
ClusterTriggerAuthentication
objects (#1452)MIN/MAX
replica counts when using kubectl get scaledobject/scaledjob
(#1534)vhostName
in the metadata (#1451)getLagForPartition
function (#1464)WATCH_NAMESPACE
environment variable to the operator (#1474)None.
Published by zroubalik almost 4 years ago
Today, we are happy to announce another milestone - KEDA 2.0 is now generally available and ready to scale all your workloads! 🎊
Learn more about this release in our blog post and easily get started.
CustomResource
that implements Scale
subresource (#703)v2beta1
to v2beta2
for HPA (#721)kubectl get scaledobject
to show related trigger authentication (#777)kubectl get triggerauthentication
to show information about configured parameters (#778)We are making some breaking changes, but you can easily migrate with our migration guide.
apiGroup
from keda.k8s.io
to keda.sh
(#552)apiextensions.k8s.io/v1
instead of apiextensions.k8s.io/v1beta1
FromEnv
added. e.g: connection
-> connectionFromEnv
New()
and Close()
from the interface of service ExternalScaler
in externalscaler.proto
.Changes in our scalers:
queueLength
is now called messageCount
(#1109)host
instead of apiHost
in rabbitmq
scaler. Add protocol
in trigger spec to specify which protocol should be used (#1115)Published by zroubalik almost 4 years ago
We're happy to release KEDA 2.0.0 release candidate 2 (RC2) which is an incremental release to v2.0.0-rc. 🎉
Our goal is to release KEDA 2.0.0 stable in a couple of weeks.
apiextensions.k8s.io/v1
instead of apiextensions.k8s.io/v1beta1
Published by tomkerkhove about 4 years ago
We're happy to release KEDA 2.0.0 release candidate (RC) which is an incremental release to v2.0.0-beta. 🎉
Our goal is to release KEDA 2.0.0 stable in mid-October.
We'll provide a full changelog later today after everything is released.
apiextensions.k8s.io/v1
instead of apiextensions.k8s.io/v1beta1
None.
Published by tomkerkhove about 4 years ago
v2beta1
to v2beta2
for HPA (#721)kubectl get scaledobject
to show related trigger authentication (#777)kubectl get triggerauthentication
to show information about configured parameters (#778)apiGroup
from keda.k8s.io
to keda.sh
(#552)New()
and Close()
from the interface of service ExternalScaler
in externalscaler.proto
.FromEnv
added. e.g: connection
-> connectionFromEnv
queueLength
is now called messageCount
(#1109)host
instead of apiHost
in rabbitmq
scaler. Add protocol
in trigger spec to specify which protocol should be used (#1115)Published by tomkerkhove over 4 years ago
nodeSelector
in raw YAML deployment specifications (Details)includeUnacked
in RabbitMQ scaler (Details)BlobEndpoint
, QueueEndpoint
, TableEndpoint
& FileEndpoint
segments (Details)queueLength
optional in RabbitMQ scaler (Details)None.
None.
Published by tomkerkhove over 4 years ago
None
None.
Published by SatishRanjan over 4 years ago
License has changed from MIT to Apache 2.0 as per our CNCF donation.
Scalers:
Improvements:
Misc:
Published by SatishRanjan over 4 years ago
License has changed from MIT to Apache 2.0 as per our CNCF donation.
Scalers:
Improvements:
Misc:
Published by SatishRanjan over 4 years ago
New scalers:
Scalers improvments:
Misc:
Published by ahmelsayed almost 5 years ago
Published by jeffhollan almost 5 years ago
The KEDA team is thrilled to announced our 1.0 release 🎉
The team feels confident you can begin to use KEDA in production workloads. We couldn't have gotten here without the support and contributions of the community.
host
property now must resolve from a secret (#347)If you have any additional issues, feel free to report. You can also pin to kedacore/keda:0.2
for a version of KEDA before major breaks and refactoring was introduced.
Thank you to all those who have contributed through feedback, docs, code, scalers, and more. We look forward to improving the event driven on Kubernetes story moving forward. Please see our contribution guide if you are interested in contributing moving forward.