Skip to content
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

Openshift is stuck with KEDA v2.7.1 #222

Open
vku-ibm opened this issue Apr 8, 2024 · 0 comments
Open

Openshift is stuck with KEDA v2.7.1 #222

vku-ibm opened this issue Apr 8, 2024 · 0 comments

Comments

@vku-ibm
Copy link

vku-ibm commented Apr 8, 2024

This isn't a feature request but neither is an actual bug report, at least not with the operator itself.

Currently observing that Openshift instances on IBM Cloud and on AWS are pretty much stuck with KEDA v2.7.1, if operator is installed from the Hub.
On a different cluster (on-prem) we deployed KEDA using helm, it's running KEDA 2.12.1 as expected.
Perhaps some note is needed in the readme to raise awareness that Hub installation can be problematic. Message on Hub does say (Depricated) but it was working just fine until the semi-recent kubernetes upgrade on the openshift.

With a manual install one needs to be aware that KEDA version have to be matched with a proper kubernetes versions, to avoid this:

xxxxx INFO setup Running on Kubernetes 1.25 {"version": "v1.25.16+a4e782e"}
xxxxx INFO setup WARNING: KEDA 2.12.1 hasn't been tested on Kubernetes v1.25.16+a4e782e

Found the link to the mapping:
https://keda.sh/docs/2.13/operate/cluster/

edit: we used helm for the on-prem deployment, not the operator

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant