According to the CRI Networking Specification[1], the runtime shim is
responsible of managing pod's network life cycle. However, the current
CRI API doesn't expose options like network-plugin, cni-bin-dir, or
cni-conf-dir.
This adds a new --net option to the rktlet so users can specify what
network they want to use for pods. We rely on rkt to set up the network
so these are the paths where rkt looks for CNI configurations and
binaries:
Network configurations: /etc/rkt/net.d
Plugin binaries: /usr/lib/rkt/plugins/net
Note that rkt also includes some plugins[2] in the default stage1.
dongsupark
commented
7 years ago
According to the CRI Networking Specification[1], the runtime shim is responsible of managing pod's network life cycle. However, the current CRI API doesn't expose options like
network-plugin,cni-bin-dir, orcni-conf-dir.This adds a new
--netoption to the rktlet so users can specify what network they want to use for pods. We rely on rkt to set up the network so these are the paths where rkt looks for CNI configurations and binaries:/etc/rkt/net.d/usr/lib/rkt/plugins/netNote that rkt also includes some plugins[2] in the default stage1.