-
Bug
-
Resolution: Unresolved
-
Major
-
None
-
4.15.z
-
No
-
8
-
False
-
Description of problem:
The documentation does *not* list the `vlanID` attribute as an attribute that must have the same value on all NADs pointing to the same network.
Thus, the user is mislead into thinking it can have different values in the multiple NADs sharing the same network name.
Version-Release number of selected component (if applicable):
4.15.Z
How reproducible:
Always.
Steps to Reproduce:
1.
2.
3.
Actual results:
... This ensures that pods making use of the NetworkAttachmentDefinition on their own different namespaces can communicate over the same secondary network. However, those two different NetworkAttachmentDefinitions must also share the same network specific parameters such as topology, subnets, mtu, and excludeSubnets.
Expected results:
... This ensures that pods making use of the NetworkAttachmentDefinition on their own different namespaces can communicate over the same secondary network. However, those two different NetworkAttachmentDefinitions must also share the same network specific parameters such as topology, subnets, mtu, excludeSubnets, and vlanID (only relevant on localnet topology).
Additional info:
the `vlanID` attribute must be listed in the attributes that "must also share the same network specific parameters". This is written in table 8, in section [0].
[0] - https://docs.openshift.com/container-platform/4.15/networking/multiple_networks/configuring-additional-network.html#configuration-ovnk-network-plugin-json-object_configuring-additional-network
