To provide upgrade channel for Operator #1569
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
cniackz
force-pushed
the
provide-upgrade-channel
branch
from
ef0c3a5
to
b4d1368
Compare
cniackz
requested review from
harshavardhana,
dvaldivia,
pjuarezd,
reivaj05,
shtripat,
prakashsvmx and
allanrogerr
pjuarezd
previously approved these changes
Apr 17, 2023
shtripat
reviewed
Apr 17, 2023
cniackz
force-pushed
the
provide-upgrade-channel
branch
from
b4d1368
to
06fa2ed
Compare
pjuarezd
approved these changes
Apr 18, 2023
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.
Why is needed:
We need to provide an upgrade method when installing via OperatorHub so that the user can move forward with our Operator every time there is a new release. They can decide if it is automatically or manual but the upgrade channel is a must once installed. Otherwise, they will get trapped in one version only.
How it looks: