Linux kernel 3.10 or later with required dependencies. The following distributions have the required kernel, its dependencies, and are known to work well with Calico and Kubernetes.
- RedHat Linux 7
- CentOS 7
- CoreOS Container Linux stable
- Ubuntu 16.04
- Debian 8
Calico v3.1 requires a key/value store accessible by all Calico components. On Kubernetes, you can configure Calico to access an etcdv3 cluster directly or to use the Kubernetes API datastore.
Calico requires the network to allow the following types of traffic.
* Our manifests enable IPIP by default. If you disable IPIP, you won’t need to allow IPIP traffic. Refer to Configuring IP-in-IP for more information.
Tip: On GCE, you can allow this traffic using firewall rules. In AWS, use EC2 security group rules.
We test Calico v3.1 against the following Kubernetes versions.
Other versions are likely to work, but we do not actively test Calico v3.1 against them.
CNI plug-in enabled
Calico is installed as a CNI plugin. The kubelet must be configured
to use CNI networking by passing the
--network-plugin=cni argument. (On
kubeadm, this is the default.)
Other network providers
Calico must be the only network provider in each cluster. We do not currently support migrating a cluster with another network provider to use Calico networking.
Supported kube-proxy modes
Calico supports the following kube-proxy modes:
ipvs(beta) Requires Kubernetes >=v1.9.3. Refer to Enabling IPVS in Kubernetes for more details.
IP pool configuration
The IP range selected for pod IP addresses cannot overlap with any other IP ranges in your network, including:
- The Kubernetes service cluster IP range
- The range from which host IPs are allocated
Tip: If you are using one of the recommended distributions, you will already satisfy these.
ipip(if using Calico networking)