namespace: adding a dedicated entry for operator namespace in common #13080
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.
Description of your changes:
Up to this point, we've been using a single entry for the namespace, which works perfectly when utilizing the default 'rook-ceph' namespace. However, when a user attempts to adhere to the documentation to use alternative namespaces for both the operator and the cluster, they fail because our common YAML file only has a single namespace for the cluster. To solve this issue, users must create the operator namespace manually in case it's different from the cluster namespace.
Closes: #13079
Related: #11883
Which issue is resolved by this Pull Request:
Resolves #
Checklist: