cni spec expanded

Open whustone opened this issue 8 years ago • 2 comments

Hello, everyone. When we use CNI, we find that the NIC of the container may communicate though the specified NIC in nodes. Is it possible to expand CNI return? add "ref_nic" in the interfaces such as: "interfaces": [ (this key omitted by IPAM plugins) { "name": "<name>", "mac": "<MAC address>", (required if L2 addresses are meaningful) "sandbox": "<netns path or hypervisor identifier>", (required for container/hypervisor interfaces, empty/omitted for host interfaces) "ref_nics": "<reference nic list>" (such as "eth3,eth4", splited by comma) } ]

Feb 01 '18 02:02 whustone

We've been thinking about this - adding the index of the peer IF. What exactly, in your mind, is the role of the ref_nic?

Feb 08 '18 14:02 squeed

ping @whustone - waiting on you to add more information

Apr 04 '18 15:04 bboreham