What this PR does / why we need it:
enhancement on cp2 control namespace cleanup
case1: all namespace cleanup
in this case, we cleanup podpresets CR and secretshare CR in all namespaces
case2: tenant namespace cleanup
in this case, we cleanup podpresets CR and secretshare CR in tenant namespaces
case3: edge case(in rerun we not found namespace-scope cm)
in this case, since namespace-scope cm is empty it means there is only one cs-operator in the cluster, so it is safe to cleanup podpresets CR and secretshare CR in all namespace
Needs approval from an approver in each of these files:
- ~~[OWNERS](https://github.com/IBM/ibm-common-service-operator/blob/scripts-dev/OWNERS)~~ [Daniel-Fan,qpdpQ]
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: enhancement on cp2 control namespace cleanup
case1: all namespace cleanup
in this case, we cleanup podpresets CR and secretshare CR in all namespaces
case2: tenant namespace cleanup
in this case, we cleanup podpresets CR and secretshare CR in tenant namespaces
case3: edge case(in rerun we not found namespace-scope cm)
in this case, since namespace-scope cm is empty it means there is only one cs-operator in the cluster, so it is safe to cleanup podpresets CR and secretshare CR in all namespace
Which issue(s) this PR fixes: Fixes # https://github.ibm.com/IBMPrivateCloud/roadmap/issues/64063