-
Bug
-
Resolution: Unresolved
-
Minor
-
None
-
4.14
-
No
-
False
-
-
Release Note Not Required
-
In Progress
Description of problem:
Table located here has confusing documentation for `subnet` field: https://docs.openshift.com/container-platform/4.14/networking/multiple_networks/configuring-additional-network.html#configuration-ovnk-network-plugin-json-object_configuring-additional-network
I spoke with the developer mduarted@redhat.com on slack here: https://redhat-internal.slack.com/archives/CFFSAHWHF/p1707942367639669?thread_ts=1706648560.856949&cid=CFFSAHWHF
After back and forth discussion, I believe this points are important for user understanding of the config field:
- OVN-K manages IP assignment on behalf of the user. You cannot use external IPAM
- This can be any CIDR the user desires
- for layer2 topology, users can have duplicate CIDRs between NADs; this is because separate overlays are disconnected
I believe this clarifications are important for users based on my own experience trying to use and configure the feature for L2 network connectivity. Knowing definitively that I can use any CIDR I want and that I can even reuse CIDRs empowers me as a user.
Without that info, I am in the dark and just have to guess/hope that it works how I want it to, with no promise that it will.
I did not check official openshift docs outside of the 4.14 doc to see whether these changes need to be backported to other versions.