Periodically refresh CNI configuration

[caseydavenport]

Hopefully this is the right place to raise this.

Recently had some users hitting this issue: projectcalico/calico#2200

It turned out to be that when using containerd with Kubernetes, CNI config file changes on disk are not picked up without a restart of containerd.

When using docker, CNI config is periodically reloaded, and so changes are picked up for future containers. It would be great if the same was true when using containerd as the runtime.

[mikebrow]

What release are you on? We fixed this last June. When a pod is created we use the current cni config files for that pod, which is attached to the network namespace of the pod.. which is used for the containers in the pod..

[mikebrow]

See #825 :-)

[caseydavenport]

@mikebrow thanks for the pointer, I think it is likely that an older version is in use then. I'll double check and report back here.

[caseydavenport]

Yep, looks like it was an older version. Sorry for the noise - thanks!