Illumina Innovates with Rancher and Kubernetes
RKE provides the following network plug-ins that are deployed as add-ons:
By default, the network plug-in is canal. If you want to use another network plug-in, you need to specify which network plug-in to enable at the cluster level in the cluster.yml.
# Setting the flannel network plug-in
The images used for network plug-ins are under the system_images directive. For each Kubernetes version, there are default images associated with each network plug-in, but these can be overridden by changing the image tag in system_images.
You can disable deploying a network plug-in by specifying none to the network plugin directive in the cluster configuration.
Besides the different images that could be used to deploy network plug-ins, certain network plug-ins support additional options that can be used to customize the network plug-in.
By setting the canal_iface, you can configure the interface to use for inter-host communication.
The canal_flannel_backend_type option allows you to specify the type of flannel backend to use. By default the vxlan backend is used.
By setting the flannel_iface, you can configure the interface to use for inter-host communication.
The flannel_backend_type option allows you to specify the type of flannel backend to use. By default the vxlan backend is used.
Calico currently only supports 2 cloud providers, AWS or GCE, which can be set using calico_cloud_provider.
Weave encryption can be enabled by passing a string password to the network provider config.