Version: 3.18 (latest)

Rancher UI

Big picture

Install Calico Enterprise on RKE2 using the Rancher UI (Rancher Manager).

Before you begin

note

To install Calico Enterprise using Rancher UI, you must provision a base RKE2 cluster with Calico Open Source, then upgrade to Calico Enterprise. This is required because Rancher UI does not provide an option to set the RKE2 CNI value as none, which is required to install a non-default CNI like Calico Enterprise.

CNI support

Calico CNI for networking with Calico Enterprise network policy:

The geeky details of what you get:

Policy	IPAM	CNI	Overlay	Routing	Datastore

Required

A compatible cluster that can host the Rancher Manager with v2.6.5 or later
For help, see Rancher.
A Tigera license key and credentials.
Rancher's kubectl shell with access to provisioned cluster.

Prepare a Calico Open Source cluster

Provision an RKE2 cluster using Calico as the CNI and default config options.
Validate that the RKE2 cluster is set up and running.
In Rancher UI, open a kubectl shell for the cluster, and perform the next steps.
Annotate the Calico HelmChart with helmcharts.helm.cattle.io/unmanaged=true. (This avoids Rancher resetting the CNI to Calico when the RKE2 cluster is shut down or upgraded.)
```
kubectl annotate helmchart -n kube-system rke2-calico helmcharts.helm.cattle.io/unmanaged=true
```
SSH to all the control plane nodes and rename rke2-calico.yaml in the /var/lib/rancher/rke2/server/manifests/ directory to rke2-calico.yaml.skip.
```
sudo mv /var/lib/rancher/rke2/server/manifests/rke2-calico.yaml /var/lib/rancher/rke2/server/manifests/rke2-calico.yaml.skip
```

Patch the Calico Installation resource to remove the image path prefix.

kubectl patch installation default --type='json' -p='[{"op": "remove", "path": "/spec/imagePath"},{"op": "remove", "path": "/spec/imagePrefix"}]'

Create ClusterRole and ClusterRoleBinding to allow Tigera Operator to update Pod Security Admission.

kubectl create -f - <<EOF
apiVersion: rbac.authorization.k8s.io/v1
kind: ClusterRole
metadata:
  name: tigera-operator-psa
rules:
- apiGroups:
  - management.cattle.io
  resources:
  - projects
  verbs:
  - updatepsa
---
apiVersion: rbac.authorization.k8s.io/v1
kind: ClusterRoleBinding
metadata:
  name: tigera-operator-psa
roleRef:
  apiGroup: rbac.authorization.k8s.io
  kind: ClusterRole
  name: tigera-operator-psa
subjects:
- kind: ServiceAccount
  name: tigera-operator
  namespace: tigera-operator
EOF

Upgrade to Calico Enterprise

In Rancher UI, open a kubectl shell for the cluster.
Follow the steps to upgrade Calico to Calico Enterprise in the kubectl shell

Next steps

Recommended

Recommended - Networking

The default networking uses VXLAN encapsulation with BGP routing. For all networking options, see Determine best networking option.

Recommended - Security

Get started with Calico Enterprise tiered network policy

Rancher UI

Big picture​

Before you begin​

How to​

Prepare a Calico Open Source cluster​

Upgrade to Calico Enterprise​

Next steps​