-
Bug
-
Resolution: Duplicate
-
Undefined
-
None
-
None
-
None
-
Quality / Stability / Reliability
-
0.42
-
False
-
-
False
-
None
-
-
None
Description of problem:
The Create ClusterUserDefinedNetworks dialog requests the admin to select existing projects this CUDN will match. While that in some cases this will be a useful functionality for secondary CUDNs, I believe it does not fit the expected flow of primary CUDN: 1. Admin creates a network matching an arbitrary label 2. Namespaces with matching label will be created and automatically registered into this network. These namespaces may be created right away, or much later. Point being, the namespaces may not even exist at the time of the CUDN definition.
Version-Release number of selected component (if applicable):
4.18 rc.8
How reproducible:
Always
Steps to Reproduce:
1. Open the ClusterUserDefinedNetworks dialog
Actual results:
It only allows me to select existing namespaces
Expected results:
It should allow me to select an arbitrary label. Selection of projects may stay too.
Additional info:
- duplicates
-
CNV-55239 CUDN dialog requires selection of existing projects
-
- Closed
-