OLM installation fallback to normal installation without warning #2105
Comments
squakez
added a commit
to squakez/camel-k
that referenced
this issue
Mar 11, 2021
Printing an error message telling the user OLM is not available if that was selected during installation Fixes apache#2105
squakez
added a commit
to squakez/camel-k
that referenced
this issue
Mar 12, 2021
Printing an error message telling the user OLM is not available if that was selected during installation Fixes apache#2105
squakez
added a commit
to squakez/camel-k
that referenced
this issue
Mar 15, 2021
Printing an error message telling the user OLM is not available if that was selected during installation Fixes apache#2105
astefanutti
pushed a commit
that referenced
this issue
Mar 16, 2021
Printing an error message telling the user OLM is not available if that was selected during installation Fixes #2105
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I am not sure if this is a regression or the intended behavior. Basically when I try to install the operator via OLM and OLM is not installed to the cluster, the procedure silently fallback to the normal installation. So, as a user I think I've installed via OLM, when I really have installed the bundled operator. I wonder if it's an error and if it's not I think we should at least warn the user about that.
The text was updated successfully, but these errors were encountered: