All Kubernetes versions listed are e2e tested and guaranteed to be compatible with this Cilium version. Older Kubernetes versions not listed here do not have Cilium support. Newer Kubernetes versions, while not listed, will depend on the backward compatibility offered by Kubernetes.
Cilium requires a Linux kernel >= 4.9. See System Requirements for the full details on all systems requirements.
Enable CNI in Kubernetes¶
CNI - Container Network Interface is the plugin layer used by Kubernetes to
delegate networking configuration. CNI must be enabled in your Kubernetes
cluster in order to install Cilium. This is done by passing
--network-plugin=cni to kubelet on all nodes. For more information, see
the Kubernets CNI network-plugins documentation.
The Installation with managed etcd relies on the etcd-operator to manage an
etcd cluster. In order for the etcd cluster to be available, the Cilium pod is
being run with
dnsPolicy: ClusterFirstWithHostNet in order for Cilium to be
able to look up Kubernetes service names via DNS. This creates a dependency on
kube-dns. It is possible to avoid this dependency by deploying Cilium with
etcd.k8sService=true. This option will allow Cilium to perform the name
translation automatically by checking the service IP of the service name for
the etcd cluster. This service name is usually in the form of
and it is automatically created by Cilium etcd Operator.
For more information about
dnsPolicy see: https://firstname.lastname@example.org/core/v1#DNSPolicy
Enable automatic node CIDR allocation (Recommended)¶
Kubernetes has the capability to automatically allocate and assign a per node IP
allocation CIDR. Cilium automatically uses this feature if enabled. This is the
easiest method to handle IP allocation in a Kubernetes cluster. To enable this
feature, simply add the following flag when starting
This option is not required but highly recommended.