-
Notifications
You must be signed in to change notification settings - Fork 345
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
Avoid installing operator when OLM reaources are present #1223
Milestone
Comments
nicolaferraro
added a commit
to nicolaferraro/camel-k
that referenced
this issue
Feb 10, 2020
nicolaferraro
added a commit
to nicolaferraro/camel-k
that referenced
this issue
Feb 10, 2020
nicolaferraro
added a commit
to nicolaferraro/camel-k
that referenced
this issue
Feb 10, 2020
nicolaferraro
added a commit
to nicolaferraro/camel-k
that referenced
this issue
Feb 10, 2020
nicolaferraro
added a commit
to nicolaferraro/camel-k
that referenced
this issue
Feb 10, 2020
nicolaferraro
added a commit
to nicolaferraro/camel-k
that referenced
this issue
Feb 10, 2020
astefanutti
pushed a commit
that referenced
this issue
Feb 12, 2020
astefanutti
pushed a commit
that referenced
this issue
Feb 12, 2020
astefanutti
pushed a commit
that referenced
this issue
Feb 12, 2020
astefanutti
pushed a commit
that referenced
this issue
Feb 12, 2020
astefanutti
pushed a commit
that referenced
this issue
Feb 12, 2020
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
We can lookup the namespace to find OLM resources indicating that an operator is already running and avoid installing another operator on 'kamel install'.
We should also notify the user and provide a way to force the installation.
The text was updated successfully, but these errors were encountered: