feat(cmd): OLM default discovery #2735
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
oscerd
approved these changes
Nov 8, 2021
astefanutti
reviewed
Nov 8, 2021
astefanutti
approved these changes
Nov 8, 2021
If the cluster which we are connected is a plain K8S cluster, we will use Operator SDK community parameters during OLM installation procedure. Closes apache#2113
|
The E2E are failing because: not related to this PR and reported in #2742. I am going to merge if there is no objection. |
tadayosi
approved these changes
Nov 11, 2021
Closed
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
If the cluster which we are connected is a plain K8S cluster, we will use Operator SDK community parameters during OLM installation procedure.
With this PR we're discovering the cluster type dynamically and provide the proper OLM configuration during install/uninstall phase.
Closes #2113
Release Note