-
Notifications
You must be signed in to change notification settings - Fork 1.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Release: 2.13.0 #5275
Comments
Added the blocker ones to the 2.13 milestone of our roadmap with high prio |
quick update regarding some of the items
intending to tackle in #5360
handled by @tomkerkhove already in #5018 |
Holding off creating a release until these are merged: |
#5377 is still open so will start release early tomorrow morning CEST |
There are open Helm chart PRs that we should consider for the release: |
I've just reviewed them (because sadly I was the blocker on almost all of them). |
Tag created, build ongoing: https://github.com/kedacore/keda/actions/runs/7580118918 |
Should we include this PR #5407? |
docs PR freshly rebased to include latest merged commits, ptal |
I tried to prepare the helm release as well, ptal |
I did not wait for it since we did not identify as a blocking feature, sorry =) |
Release notes and discussion updated with changelog: https://github.com/kedacore/keda/releases/tag/v2.13.0 |
Images imported in Snyk |
Hotfix branch: https://github.com/kedacore/keda/tree/release/v2.13 |
We should be good to go, he only remaining aspect is Helm chart + announcement which I will do once chart is ready. @wozniakjan feel free to take your time, I'm on CNCF slack if you need me. |
thanks @tomkerkhove, I believe I have clarity regarding both CRD diff as well as webhook disablement option. Ptal if kedacore/charts#593 is ready to merge. |
Helm is merged and published release notes |
And I think that it's time for the 1st hotfix: 2024/01/19 11:51:06 maxprocs: Updating GOMAXPROCS=1: using minimum allowed GOMAXPROCS
2024-01-19T11:51:06Z INFO setup Starting manager
2024-01-19T11:51:06Z INFO setup KEDA Version: 2.13.0
2024-01-19T11:51:06Z INFO setup Git Commit: 367fcd32f1e72be504ada53165d07c33d75fc0f7
2024-01-19T11:51:06Z INFO setup Go Version: go1.21.6
2024-01-19T11:51:06Z INFO setup Go OS/Arch: linux/amd64
2024-01-19T11:51:06Z INFO setup Running on Kubernetes 1.27 {"version": "v1.27.7"}
2024-01-19T11:51:07Z INFO starting server {"kind": "health probe", "addr": "[::]:8081"}
I0119 11:51:07.055862 1 leaderelection.go:250] attempting to acquire leader lease keda/operator.keda.sh...
2024-01-19T11:51:07Z INFO controller-runtime.metrics Starting metrics server
2024-01-19T11:51:07Z INFO controller-runtime.metrics Serving metrics server {"bindAddress": ":8080", "secure": false}
E0119 11:51:24.388650 1 leaderelection.go:369] Failed to update lock: leases.coordination.k8s.io "operator.keda.sh" is forbidden: User "system:serviceaccount:keda:keda-operator" cannot update resource "leases" in API group "coordination.k8s.io" in the namespace "keda"
E0119 11:51:27.052988 1 leaderelection.go:369] Failed to update lock: leases.coordination.k8s.io "operator.keda.sh" is forbidden: User "system:serviceaccount:keda:keda-operator" cannot update resource "leases" in API group "coordination.k8s.io" in the namespace "keda"
E0119 11:51:30.112698 1 leaderelection.go:369] Failed to update lock: leases.coordination.k8s.io "operator.keda.sh" is forbidden: User "system:serviceaccount:keda:keda-operator" cannot update resource "leases" in API group "coordination.k8s.io" in the namespace "keda"
E0119 11:51:34.269628 1 leaderelection.go:369] Failed to update lock: leases.coordination.k8s.io "operator.keda.sh" is forbidden: User "system:serviceaccount:keda:keda-operator" cannot update resource "leases" in API group "coordination.k8s.io" in the namespace "keda"
E0119 11:51:38.482921 1 leaderelection.go:369] Failed to update lock: leases.coordination.k8s.io "operator.keda.sh" is forbidden: User "system:serviceaccount:keda:keda-operator" cannot update resource "leases" in API group "coordination.k8s.io" in the namespace "keda"
E0119 11:51:41.628618 1 leaderelection.go:369] Failed to update lock: leases.coordination.k8s.io "operator.keda.sh" is forbidden: User "system:serviceaccount:keda:keda-operator" cannot update resource "leases" in API group "coordination.k8s.io" in the namespace "keda"
E0119 11:51:45.826308 1 leaderelection.go:369] Failed to update lock: leases.coordination.k8s.io "operator.keda.sh" is forbidden: User "system:serviceaccount:keda:keda-operator" cannot update resource "leases" in API group "coordination.k8s.io" in the namespace "keda"
E0119 11:51:49.208734 1 leaderelection.go:369] Failed to update lock: leases.coordination.k8s.io "operator.keda.sh" is forbidden: User "system:serviceaccount:keda:keda-operator" cannot update resource "leases" in API group "coordination.k8s.io" in the namespace "keda"
E0119 11:51:52.240208 1 leaderelection.go:369] Failed to update lock: leases.coordination.k8s.io "operator.keda.sh" is forbidden: User "system:serviceaccount:keda:keda-operator" cannot update resource "leases" in API group "coordination.k8s.io" in the namespace "keda" I guess that it's related with : 367fcd3 |
Please open an issue on the Helm repo for this |
Yeah, I'm trying to figure out why this passed e2e test on KEDA side but it's failing using helm |
Looks like an RBAC issue in the Helm chart |
The release is done 🎉 Thanks for the valuable help, @wozniakjan! |
Let's follow-up there, likely this requires Helm hotfix only |
This issue template is used to track the rollout of a new KEDA version.
For the full release process, we recommend reading this document.
Required items
Nice to have
LimitRange
forScaledObject
validations #5377Not needed
- [ ] Refactor get config togetParameterFromConfigV2
Kafka Scaler #5319Timeline
We aim to release this release in the week of January 11.
Progress
The text was updated successfully, but these errors were encountered: