Rancher Kubernetes Engine (RKE)
Install Calico as the required CNI for networking and/or network policy on Rancher-deployed clusters.
Calico supports the Calico CNI with Calico network policy:
The geeky details of what you get:
Before you begin
A compatible Rancher Kubernetes Engine cluster with version 1.3
RKE cluster meets the Calico requirements
kubectlenvironment with access to your cluster
- Use Rancher kubectl Shell for access
- Ensure you have the Kubeconfig file that was generated when you created the cluster.
If using a Kubeconfig file locally, install and set up the Kubectl CLI tool.
Install the Tigera Calico operator and custom resource definitions.
kubectl create -f https://raw.githubusercontent.com/projectcalico/calico/v3.26.4/manifests/tigera-operator.yamlnote
Due to the large size of the CRD bundle,
kubectl applymight exceed request limits. Instead, use
Install Calico by creating the necessary custom resource. For more information on configuration options available in this manifest, see the installation reference.
kubectl create -f https://raw.githubusercontent.com/projectcalico/calico/v3.26.4/manifests/custom-resources.yamlnote
Before creating this manifest, read its contents and make sure its settings are correct for your environment. For example, you may need to change the default IP pool CIDR to match your pod network CIDR. Rancher uses
If you are installing Calico on Windows nodes in this cluster, please see the Calico for Windows for RKE installation instructions.
Confirm that all of the pods are running with the following command.
watch kubectl get pods -n calico-system
Wait until each pod has the
Congratulations! You now have an RKE cluster running Calico