github.com/imran-kn/cilium-fork@v1.6.9/Documentation/gettingstarted/flannel-integration.rst (about) 1 .. only:: not (epub or latex or html) 2 3 WARNING: You are looking at unreleased Cilium documentation. 4 Please use the official rendered version released here: 5 http://docs.cilium.io 6 7 .. _flannel-integration: 8 9 ************************************** 10 Cilium integration with Flannel (beta) 11 ************************************** 12 13 This guide contains the necessary steps to run Cilium on top of your Flannel 14 cluster. 15 16 If you have a cluster already set up with Flannel you will not need to install 17 Flannel again. 18 19 This Cilium integration with Flannel was performed with Flannel 0.10.0 and 20 Kubernetes >= 1.9. If you find any issues with previous Flannel versions please 21 feel free to reach out to us to help you. 22 23 .. note:: 24 25 This is a beta feature. Please provide feedback and file a GitHub issue if 26 you experience any problems. 27 28 The feature lacks support of the following, which will be resolved in 29 upcoming Cilium releases: 30 31 - L7 policy enforcement 32 33 34 Flannel installation 35 -------------------- 36 37 NOTE: If ``kubeadm`` is used, then pass ``--pod-network-cidr=10.244.0.0/16`` to 38 ``kubeadm init`` to ensure that the ``podCIDR`` is set. 39 40 .. parsed-literal:: 41 42 kubectl apply -f \ |SCM_WEB|\/examples/kubernetes/addons/flannel/flannel.yaml 43 44 45 Wait until all pods to be in ready state before preceding to the next step. 46 47 Cilium installation 48 ------------------- 49 50 .. include:: k8s-install-download-release.rst 51 52 Generate the required YAML file and deploy it: 53 54 .. code:: bash 55 56 helm template cilium \ 57 --namespace kube-system \ 58 --set global.flannel.enabled=true \ 59 > cilium.yaml 60 61 Set ``global.flannel.uninstallOnExit=true`` if you want Cilium to uninstall 62 itself when the Cilium pod is stopped. 63 64 If the Flannel bridge has a different name than ``cni0``, you must specify 65 the name by setting ``global.flannel.masterDevice=...``. 66 67 *Optional step:* 68 If your cluster has already pods being managed by Flannel, there is also 69 an option available that allows Cilium to start managing those pods without 70 requiring to restart them. To enable this functionality you need to set the 71 value ``global.flannel.manageExistingContainers=true`` 72 73 Once you have changed the ConfigMap accordingly, you can deploy Cilium. 74 75 .. parsed-literal:: 76 77 kubectl create -f cilium.yaml 78 79 Cilium might not come up immediately on all nodes, since Flannel only sets up 80 the bridge network interface that connects containers with the outside world 81 when the first container is created on that node. In this case, Cilium will wait 82 until that bridge is created before marking itself as Ready.