Releases: kedacore/keda
Releases · kedacore/keda
KEDA 1.1.0
Release notes:
New scalers:
- Provide support for Huawei Cloud CloudEye scaler (#478)
- Add kinesis stream scaler (#526)
- Add azure blob scaler (#514)
Scalers improvments:
- Add unique name for aws-sqs-queue metrics (#475)
- add kafka scaler sasl (#486)
- Event Hub scalar expansion to work with Java and C# applications (#517)
- Escape Prometheus querystring (#521)
- Change how number of pending messages is calculated and add more error handling. (#533)
- Service bus scaler pod identity fix (#534)
- Eventhub scalar fix (#537)
- Kafka scaler fix for SASL plaintext auth (#544)
Misc:
- ScaledObject Status clean up (#466)
- add default log level for operator (#468)
- ensure get the metrics that have been aggregated (#509)
- scale from zero when minReplicaCount is > 0 (#524)
- Total running Jobs must not exceed maxScale - Running jobs (#528)
- check deploymentName definition in ScaledObject (#532)
KEDA 1.0.0
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.
KEDA Resources
Improvements from the v0.x releases
- Many more scalers added
- Scaler extensibility (run scalers in a different container and communicate with KEDA via gRPC)
- TriggerAuthentication and Pod Identity for identity based auth that can be shared across deployments
- Schedule jobs on events in addition scaling out deployments
- Additional tests and automation through GitHub Actions
Breaking changes from v0.x releases
- RabbitMQ
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!
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.