[LTSR] avoid OperandBindInfo label conflict #934
Merged
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.
for ticket: https://github.ibm.com/IBMPrivateCloud/roadmap/issues/58807
An easier way to all multiple operandBindInfos mounting same secret
When two operandBindInfos are watching same secret/configmap, they are adding the same label to the secret/configmap
operator.ibm.com/watched-by-opbi-with-name: ibm-licensing-bindinfoThis pr will try to fix it by adding a number after the label key
test:
expect result:
<namespace>.<name>/bindinfo: trueThis image can be used to verify
quay.io/yuchen_li1/odlm-amd64@sha256:ba111b9726675779bbdaafd6bfcbf583d6049d609686b70b3e4b43c0c285fcaatest looks good to me: