-
Notifications
You must be signed in to change notification settings - Fork 23
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
Comments
Red Hat no longer does KEDA releases in their catalog but does provide Custom Metrics Autoscaler, which is the downstream, Red Hat branded version of KEDA. If you don't want to run Custom Metrics Autoscaler but would like to run KEDA on OpenShift and deploy via the OLM operator, you should add the Kubernetes Community Operators repo as a catalog source, which will allow you to install the KEDA OLM operator. |
fyi
Viktor Kuropiatnyk
Software Engineer ? AI4K
IBM Research GmbH
S?umerstrasse 4
8803 R?schlikon
Switzerland
From: Joel Smith ***@***.***>
Date: Tuesday, 18 June 2024 at 21:31
To: kedacore/keda-olm-operator ***@***.***>
Cc: Viktor Kuropiatnyk ***@***.***>, Author ***@***.***>
Subject: [EXTERNAL] Re: [kedacore/keda-olm-operator] Openshift is stuck with KEDA v2.7.1 (Issue #222)
Red Hat no longer does KEDA releases in their catalog but does provide Custom Metrics Autoscaler, which is the downstream, Red Hat branded version of KEDA. If you don't want to run Custom Metrics Autoscaler but would like to run KEDA on OpenShift
Red Hat no longer does KEDA releases in their catalog but does provide Custom Metrics Autoscaler, which is the downstream, Red Hat branded version of KEDA. If you don't want to run Custom Metrics Autoscaler but would like to run KEDA on OpenShift and deploy via the OLM operator, you should add the Kubernetes Community Operators repo<https://olm.operatorframework.io/docs/concepts/crds/catalogsource/#example---operatorhubio> as a catalog source, which will allow you to install the KEDA OLM operator.
?
Reply to this email directly, view it on GitHub<#222 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AYWG2B6LDIRTKHKWFFHJTWLZICDJHAVCNFSM6AAAAABF4U3NNGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCNZWHAYTINRSGQ>.
You are receiving this because you authored the thread.Message ID: ***@***.***>
|
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:
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
The text was updated successfully, but these errors were encountered: