-
Notifications
You must be signed in to change notification settings - Fork 31
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
operator: Multiple same operators installed test #2542
Merged
sebrandon1
merged 1 commit into
redhat-best-practices-for-k8s:main
from
sebrandon1:multiple_same_operators
Nov 4, 2024
Merged
operator: Multiple same operators installed test #2542
sebrandon1
merged 1 commit into
redhat-best-practices-for-k8s:main
from
sebrandon1:multiple_same_operators
Nov 4, 2024
+99
−7
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
sebrandon1
force-pushed
the
multiple_same_operators
branch
from
October 28, 2024 19:28
92fb6d1
to
abbb13d
Compare
from change #2542: |
sebrandon1
force-pushed
the
multiple_same_operators
branch
from
October 28, 2024 21:54
abbb13d
to
94b4021
Compare
from change #2542: |
greyerof
approved these changes
Oct 30, 2024
from change #2542: |
sebrandon1
force-pushed
the
multiple_same_operators
branch
2 times, most recently
from
October 31, 2024 15:35
91e290f
to
5756123
Compare
from change #2542: |
sebrandon1
force-pushed
the
multiple_same_operators
branch
from
October 31, 2024 16:43
5756123
to
f1a5ff3
Compare
from change #2542: |
sebrandon1
force-pushed
the
multiple_same_operators
branch
from
November 1, 2024 18:26
f1a5ff3
to
e1dff1b
Compare
from change #2542: |
sebrandon1
force-pushed
the
multiple_same_operators
branch
from
November 1, 2024 19:21
e1dff1b
to
06b69bf
Compare
from change #2542: |
sebrandon1
force-pushed
the
multiple_same_operators
branch
2 times, most recently
from
November 1, 2024 21:16
2b8c9f0
to
7921c23
Compare
from change #2542: |
sebrandon1
force-pushed
the
multiple_same_operators
branch
2 times, most recently
from
November 1, 2024 21:54
8bc390c
to
d1dc30f
Compare
from change #2542: |
sebrandon1
force-pushed
the
multiple_same_operators
branch
from
November 4, 2024 16:49
d1dc30f
to
579fe58
Compare
from change #2542: |
sebrandon1
merged commit Nov 4, 2024
6627858
into
redhat-best-practices-for-k8s:main
35 checks passed
from change #2542: |
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.
Adds a new mandatory test in the
operator
suite that checks to ensure the same CSV is not installed more than once. CSVs installed by OLM are uniquely namedoperator.version
format. However it is possible to have the CSV exist in more than one namespace. The best practices document forbids that from being the case.If you try to install an operator more than once in the same cluster using the UI, it prevents it with the following message:
So the only way you could get around this would be to manually apply YAMLs I would assume. I was able to do that in my own cluster.