Doug Smith

Here's an example for you: https://github.com/openshift/multus-cni/blob/master/images/entrypoint.sh#L502-L508 But, it could maybe be patched in the release-v3 branch

> my delegate CNI searches for the file /var/run/secrets/kubernetes.io/serviceaccount/token Since this is executed either on the host (via thin plugin) or within a chroot (within the thick plugin) it won't...

I kind of think there needs to be changes to userspace CNI in order to support thick plugin functionality -- especially if userspace CNI was reusing the kubeconfig from multus...

This should also probably filed against https://github.com/containernetworking/plugins

Our advice generally is to modify https://github.com/k8snetworkplumbingwg/multus-cni/blob/master/deployments/multus-daemonset-thick.yml#L246 to your liking. There's a potential to provide another example deployment, or documentation. Up for ideas as well

@micw we'd love your contributions against the helm charts -- it's one of those places where there's always more contributions necessary, you can find the charts @ https://github.com/k8snetworkplumbingwg/helm-charts And if...

It's for multi-container, I don't think I have any end-to-end testing of the AIO container, just tests if the build completes for it. But e2e tests for the multi-container actually...

I will take a @lmangani -- quick glance looks pretty great. I'll give it a whirl

Thanks for the report on this one, there's a couple things here as a todo... Firstly... RTCP info hasn't been verified on homer-docker (at least by me), so, it can...

Thanks for the extra info. No action necessary on your part, for making the new travis CI tests (unless you want to contribute, which would be much appreciated as always)....