Flannel is a virtual network that gives a subnet to each host for use with container runtimes.
This charm will deploy flannel as a background service, and configure CNI for
use with flannel, on any principal charm that implements the
The flannel charm is a
This charm will require a principal charm that implements the
interface in order to properly deploy.
juju deploy cs:~containers/flannel juju deploy cs:~containers/etcd juju deploy cs:~containers/kubernetes-master juju deploy cs:~containers/kubernetes-worker juju add-relation flannel etcd juju add-relation flannel kubernetes-master juju add-relation flannel kubernetes-worker
|cidr||string||10.1.0.0/16||Network CIDR to assign to Flannel|
|iface||string||The interface to bind flannel overlay networking. The default value is the interface bound to the cni endpoint.|
|nagios_servicegroups||string||A comma-separated list of nagios servicegroups. If left empty, the nagios_context will be used as the servicegroup|
Used by the nrpe subordinate charms. A string that will be prepended to instance name to set the host name in nagios. So for instance the hostname would be something like:
If you're running multiple environments with the same services in them this allows you to differentiate between them.
This subordinate does not support being co-located with other deployments of the flannel subordinate (to gain 2 vlans on a single application). If you require this support please file a bug.
This subordinate also leverages juju-resources, so it is currently only available on juju 2.0+ controllers.