-
Bug
-
Resolution: Done
-
Critical
-
4.13.z, 4.14.z, 4.15.z, 4.17.z, 4.16.z
-
Quality / Stability / Reliability
-
False
-
-
3
-
Critical
-
No
-
None
-
None
-
None
-
OSDOCS Sprint 255, OSDOCS Sprint 256
-
2
-
None
-
None
-
None
-
None
-
None
-
None
-
None
Description of problem:
The network named `default` is the default cluster network - in fact, that's literally the criteria to identify the default cluster network in the system. For that matter, we should call out to our users to not create a network with that name, since it risks confusing OVN-Kubernetes.
Version-Release number of selected component (if applicable):
How reproducible:
Always
Steps to Reproduce:
1. 2. 3.
Actual results:
We should ensure ours users know they should not be naming their networks `default`.
Expected results:
A callout indicating the network name can never be `default`.
Additional info:
I think the right way is to provide a note/callout in this section: https://docs.openshift.com/container-platform/4.15/networking/multiple_networks/configuring-additional-network.html#configuration-ovnk-additional-networks_configuring-additional-network
- links to
(1 links to)
