-
Bug
-
Resolution: Unresolved
-
Undefined
-
None
-
4.18.0
-
None
-
Quality / Stability / Reliability
-
False
-
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
Description of problem:
The CUDN creation view doesnt prevent namespace-selector with no rules
Version-Release number of selected component (if applicable):
How reproducible:
always
Steps to Reproduce:
1.In the UI, go to CUDN creation view, create CDUN with empty namespace-selector.
Actual results:
The CUDN will select all namespaces exist in the cluster, including openshift-* namespaces. Affecting the cluster system components including the api-server, etcd.
Expected results:
I expect the UI to block creating CUDN with namespace-selector that has zero rules.
Additional info:
This is https://issues.redhat.com/browse/CNV-55129 moved to OCP