https://wiki.williams-net.org/index.php?action=history&feed=atom&title=Kubernetes_Flannel_Network_PluginKubernetes Flannel Network Plugin - Revision history2026-06-01T02:37:28ZRevision history for this page on the wikiMediaWiki 1.40.1https://wiki.williams-net.org/index.php?title=Kubernetes_Flannel_Network_Plugin&diff=162&oldid=prevDrEdWilliams: Transferred from main cluster controller installation page2019-12-26T21:41:44Z<p>Transferred from main cluster controller installation page</p>
<p><b>New page</b></p><div>'''''NOTE: the use of this plugin is deprecated -- these instructions are saved here for historical/archival purposes.'''''<br />
<br />
The Flannel pod networking can be installed directly from the repository using this command:<br />
<br />
kubectl apply -f https://raw.githubusercontent.com/coreos/flannel/master/Documentation/kube-flannel.yml<br />
<br />
On Kubernetes v1.16+, if there are issues (specifically, nodes don't reach the '''''Ready''''' state), try this specific version:<br />
<br />
kubectl apply -f https://raw.githubusercontent.com/coreos/flannel/2140ac876ef134e0ed5af15c65e414cf26827915/Documentation/kube-flannel.yml<br />
<br />
By default, flannel uses the primary network interface (eth0 on 10.0.0.0/24); but if you want to push the traffic onto the secondary interfaces (such as for the development cluster), download the YAML manifest and add one parameter to the argument list on/about line 190 (in the spec -> template -> spec -> containers [where name == 'kube-flannel-ds-amd64'] -> args). The result should look like this:<br />
<br />
...<br />
args:<br />
- --ip-masq<br />
- --kube-subnet-mgr<br />
- --iface=eth1<br />
resources:<br />
...<br />
<br />
substitute the secondary interface name for 'eth1' if it is different. Then apply the manifest:<br />
<br />
kubectl apply -f kube-flannel.yaml<br />
<br />
Other configuration options can be passed to flannel per [https://github.com/coreos/flannel/blob/master/Documentation/configuration.md this page]</div>DrEdWilliams