Adrian Chiris

PR #307 adds additional information around CNI

> Isn't it a bug as it is mentioned as a supported feature?: Maybe a documentation bug :) , i dont remember having this logic in DP. @ipatrykx i think...

one idea i had is to leverage PodResourceLister service exposed by kubelet[1] to add the "missing" devices. [1] https://kubernetes.io/docs/concepts/extend-kubernetes/compute-storage-net/device-plugins/#monitoring-device-plugin-resources

> I think it could be an option, just that we need to add k8s api access in device plugin. its grpc to kubelet socket so no access to k8s...

> I wonder to know whether there is some difference between this two scenarioes for pod network. if you need to have two additional network interfaces for the Pod, configured...

> if you need to have two additional network interfaces for the Pod, configured by a supporting CNI plugin then IIRC only the second scenario will work. correction, i meant...

Greetings @DmytroLinkin ! I have raised this issue in today's community meeting. As its a new technology and not a trivial change in device plugin i think it would be...

> also build and unit test at a specific time interval. I think we are now missing this bit and we can mark this as done.

@lynic the entity which is in charge to initiate the connection is kubelet[1]. SRIOV device plugin exposes two grpc services on that socket 1. plugin registration [2] 2. device plugin...

@DmytroLinkin could you rebase this PR. planning to get to it this week (fingers crossed :) )