-
Story
-
Resolution: Unresolved
-
Undefined
-
None
-
None
-
None
-
Future Sustainability
-
False
-
-
False
-
None
-
None
-
None
-
None
Typically our assumption has been that connectivity on a given secondary network is merely an attachment to an existing customer network, while this may be true, it would be useful for many users (both internal and external) to have a guide that explains how to:
- select a reference CNI plugin (e.g. ipvlan vs macvlan)
- debug connectivity issues on a network
- point people to the proper documentation when it's reasonable (e.g. to linux macvlan docs for details on what's happening at the O/S level)
Blaine Gardner made a note of these useful references:
macvlan: https://docs.docker.com/network/drivers/macvlan/
ipvlan: https://docs.docker.com/network/drivers/ipvlan/
CNI docs : https://www.cni.dev/plugins/current/main/