design rational #114
-
Hi, |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 7 replies
-
after some research, my guess is libvirtd expect to see the tap device (/dev/tapxx) for pre-created macvtap interface; however if the CNI plugin create the macvtap interface, then tap device won't show up in k8s pod, it is only on host; while a k8s device plugin will allow k8s to mount host's /dev/tapxxx to the pod; it would be nice for dev to confirm if my theory is correct |
Beta Was this translation helpful? Give feedback.
after some research, my guess is libvirtd expect to see the tap device (/dev/tapxx) for pre-created macvtap interface; however if the CNI plugin create the macvtap interface, then tap device won't show up in k8s pod, it is only on host; while a k8s device plugin will allow k8s to mount host's /dev/tapxxx to the pod;
it would be nice for dev to confirm if my theory is correct