-
Story
-
Resolution: Done
-
Major
-
None
-
None
-
Product / Portfolio Work
-
3
-
False
-
-
False
-
None
-
https://github.com/ovn-org/ovn-kubernetes/pull/4671, https://github.com/k8snetworkplumbingwg/network-attachment-definition-client/pull/69, https://github.com/k8snetworkplumbingwg/network-attachment-definition-client/pull/70, https://github.com/k8snetworkplumbingwg/network-attachment-definition-client/pull/71
-
-
None
The `k8s.v1.cni.cncf.io/network-status` annotation is missing the UDN interface.
k8s.v1.cni.cncf.io/network-status: |-
[{
"name": "ovn-kubernetes",
"interface": "eth0",
"ips": [
"10.135.0.21"
],
"mac": "0a:58:0a:87:00:15",
"default": true,
"dns": {}
},{
"name": "default/primary-udn-kubevirt-binding",
"interface": "eth0",
"mac": "0a:58:0a:87:00:15",
"dns": {}
}]
Used examples from https://gist.github.com/RamLavi/91a25858a56f87e47039ceef99df662b
and KCLI with this hack (in order to workaround the OCP stability issue when enabling TP FeatureSet)
https://gist.github.com/oshoval/10b7eab5ec3ef1eab3b1b89b50f7e7c6
