Re-create NSS CR after NSS operator upgrade in migration #2203
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.
Context
There is a corner case in
migrate_tenant.sh
whereno-op
service is requested in OperandRegistrynamespace-scope
ConfigMap only contains one namespace.Issue
CS operator will delete the NamespaceScope CR that are just created by the script. This will result no NamespaceScope CR in the tenant for permission projection.
Solution
The script will re-create the NamespaceScope CR after NSS operator is upgraded to v4.x level.
When CPFS 4.x detects NSS operator v4, it will not delete NamespaceScope CR.