ClusterUserDefinedNetworks (CUDN) introduce a new flow to network configuration. MTV should align with it, to provide smooth UX.

The CUDN flow is:

1. CUDN is created with a namespace selector
2. When a matching namespace is detected, NetworkAttachmentDefinition (NAD) gets created in it

My understanding of the MTV flow is this:

1. (optional) Destination project is created
2. Networks of destination are listed
3. Networks are mapped

What I think the flow should be now:

1. (optional) Destination project is created
2. (optional) User can add labels to the project
3. Networks of the destination are listed
4. Networks can be refreshed, manually or automatically (in case mapping was opened before the CUDN controller got a chance to created the NAD)
5. Networks are mapped

Without this adjustment, users may need to jump back and forth between menus to configure the Project, and they may need to refresh the network mapping page to see the latest list of available networks.