-
Notifications
You must be signed in to change notification settings - Fork 33
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
CLI-based install of Kuadrant Operator hangs with status Unknown #877
Comments
Yes, one of the dependencies (limitador operator especifically) was not released in 4.16. We limited to 4.12-4.14. We are working on a new release of kuadrant on the public OLM catalogs that fixes that with the latest release of kuadrant (v0.10.0). You are trying to install 0.7.1 ;) It should be a matter of few (working) days. |
BTW, you already have kuadrant v0.10.0 for bare kubernetes in operatorhub.io. Just not in Openshift community catalog yet. |
Thanks @eguzki, that's very helpful info, will try on OCP 4.14 instead. Also makes sense now why trying to install using OCP v4.16 web console selects Kuadrant v0.72, hangs with status
Looking forward to trying this again when fixed for OCP 4.16 and Kuadrant 0.10.0. |
Installing the Kuadrant Operator on OpenShift 4.16 and AWS using the install instructions gives
error executing jsonpath
instead ofcomplete
:Changing the channel to
stable
made no difference.The Operator hangs in the OCP web console with status
Unknown
andCatalogSource not found
:The
Conditions
table displays the following error underResolutionFailed
:The text was updated successfully, but these errors were encountered: