Samuel Ortiz 63c7a7c99b ocicni: Support asynchronous network config creation ... We need to support cases where InitCNI() is called before any CNI configuration files have been installed. This is for example happening when deploying a k8s cluster with kubeadm. kubeadm will start the DNS pod and it is left to the caller to pick a network overlay and create the corresponding pods, that will typically install a CNI configuration file first. Here we address that issue by doing 2 things: - Not returning an error when the default CNI config files directory is empty. - If it is empty, we start a monitoring thread (fsnotify based) that will synchronize the network configuration when a CNI file is installed there. Signed-off-by: Samuel Ortiz <sameo@linux.intel.com>		2017-04-10 17:36:28 +02:00
..
ocicni	ocicni: Support asynchronous network config creation	2017-04-10 17:36:28 +02:00
storage	read image config from docker v2s1 manifests	2017-04-04 17:52:37 +02:00