Add support for community operators #1131
Merged
Conversation
This file contains hidden or 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
dvaldivia
approved these changes
May 25, 2022
dvaldivia
approved these changes
May 27, 2022
Alevsk
approved these changes
May 27, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
I am updating Operator version from 4.4.17 to 4.4.18 in Community Operators at
k8s-operatorhub/community-operators#1241
Where all tests passed already and eventually branch will be merged by maintainers.
The relevant changes for this PR is to add support for community operators so that we can
update our operator in that particular catalog, tested already twice in two different versions:
k8s-operatorhub/community-operators#1241
k8s-operatorhub/community-operators#1212
I put the manual instructions for this Catalog in:
https://github.com/cniackz/minio/wiki/How-to-update-community-operators