Abhinandan Prativadi 263b0b99d0 Change to keep in sync with latest cni config ... This commit contains change to pick the latest cni config from the configured CNIConfDir. With this change any changes made to the cni config file will be picked up on the kubelet's runtime status check call. Ofcourse this would lead to undefined behavior when the cni config change is made in parallel during pod creation. However its reasonable to assume that the operator is aware of the need to drain the nodes of pods before making cni configuration change. The behavior is currently not defined in kubernetes. However I see that similar approach being adopted in the upstream kubernetes with dockershim. Keeping the behavior consistent for now. Signed-off-by: Abhinandan Prativadi <abhi@docker.com>		2018-06-21 20:43:38 +00:00
..
fake_cni_plugin.go	Change to keep in sync with latest cni config	2018-06-21 20:43:38 +00:00