What this PR does / why we need it:
When running the setup_singleton.sh with -- enable-private-catalog flag set, the error message of CatalogSource validation has been updated
Enhancement:
When the --enable-private-catalog flag is set, there is a warning message that prompts the namespaces of singleton operators should be in the same namespace as the singleton CatalogSource.
If the specific CatalogSource in its namespace is not found in the cluster, then the script will try to get an available global CatalogSource and will error out if there is more than one CatalogSource available in the entire cluster.
Needs approval from an approver in each of these files:
- ~~[OWNERS](https://github.com/IBM/ibm-common-service-operator/blob/scripts-dev/OWNERS)~~ [YCShen1010]
Approvers can indicate their approval by writing `/approve` in a comment
Approvers can cancel approval by writing `/approve cancel` in a comment
What this PR does / why we need it: When running the
setup_singleton.sh
with-- enable-private-catalog
flag set, the error message of CatalogSource validation has been updatedEnhancement:
--enable-private-catalog
flag is set, there is a warning message that prompts the namespaces of singleton operators should be in the same namespace as the singleton CatalogSource.Which issue(s) this PR fixes: Issue: https://github.ibm.com/IBMPrivateCloud/roadmap/issues/63998#issuecomment-83385625