Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
udn, cni: Report UDN iface info on network-status
Before this commit, this was the network status we reported for a UDN pod: ``` kubectl get pods pod -ojsonpath="{@.metadata.annotations.k8s\.v1\.cni\.cncf\.io\/network-status}" | jq [ { "name": "ovn-kubernetes", "interface": "eth0", "ips": [ "10.244.1.9", "fd00:10:244:2::9" ], "mac": "0a:58:0a:f4:01:09", "default": true, "dns": {} } ] ``` With it, we now report: ``` [ { "name": "ovn-kubernetes", "interface": "ovn-udn1", "ips": [ "10.128.0.3" ], "mac": "0a:58:0a:80:00:03", "default": true, "dns": {} }, { "name": "ovn-kubernetes", "interface": "eth0", "ips": [ "10.244.1.6", "fd00:10:244:2::6" ], "mac": "0a:58:0a:f4:01:06", "default": false, "dns": {} } ] ``` This way, applications complying to the k8snetworkplumbingwg de-facto standard can be aware of the UDN interface information. We report the primary UDN first so the network-attachment-definition-client can identify which of the 2 interfaces to report as primary [0]. [0] k8snetworkplumbingwg/network-attachment-definition-client#71 Signed-off-by: Miguel Duarte Barroso <[email protected]> Signed-off-by: Ram Lavi <[email protected]>
- Loading branch information