vbatts/cri-o
1
0
Fork 0
Code Issues Pull requests Releases Wiki Activity
cri-o/pkg/ocicni
History
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
..
LICENSE move ocicni from vendors to pkg/ 2017-01-19 17:45:54 -05:00
noop.go move ocicni from vendors to pkg/ 2017-01-19 17:45:54 -05:00
ocicni.go ocicni: Support asynchronous network config creation 2017-04-10 17:36:28 +02:00
README.md move ocicni from vendors to pkg/ 2017-01-19 17:45:54 -05:00
types.go move ocicni from vendors to pkg/ 2017-01-19 17:45:54 -05:00
util.go move ocicni from vendors to pkg/ 2017-01-19 17:45:54 -05:00

README.md

ocicni

API layer to call the CNI plugins from an OCI lifecycle daemon