System requirements
Step 1: Verify cluster
Verify that your cluster meets these requirements.
| Required | Supported |
|---|---|
| Platforms | All of the open-source Kubernetes deployments, except: - IBM Cloud Kubernetes Service (IKS) - K3s - Clusters with Windows nodes |
| Architecture | Only AMD64 |
| Kubernetes version | - Minimum: v1.23 - Maximum: v1.25 If you have a later version than the maximum, contact Support. |
| CNIs | - Calico CNI v3.15 to v3.24 - Amazon VPC CNI - Azure CNI - GKE CNI |
| Browsers for Manager UI | Calico Cloud supports the latest version and "latest minus one" versions of the following browsers: - Chrome - Firefox - Safari |
Step 2: Verify cluster is not managed by a Kubernetes reconciler
Calico Cloud cannot be installed on clusters that are managed by any kind of Kubernetes reconciler (for example, Addon-manager). To verify, look for an annotation called addonmanager.kubernetes.io/mode on either of the following resources. (The resources may not exist).
tigera-operatordeployment in thetigera-operatornamespace (Installation on AKS will work if the mode is EnsureExists)calico-nodedaemonset in thekube-systemnamespace
If the following command finds addonmanager on either of the resources, then Addon-manager is being used. Find a different cluster to use.
kubectl get <type> -n <namespace> <resource-name> -o yaml | grep ' addonmanager.kubernetes.io/mode:'
Step 3: Prepare your infrastructure to connect to Calico Cloud
Pods running in your kubernetes cluster should be allowed to connect to the following endpoints:
- https://installer.calicocloud.io:443/*
- https://www.calicocloud.io:443/api/*
- TCP to
<management-cluster>.calicocloud.io:9000
Docker running on each node should be able to pull images from quay.io,cdn01.quay.io,cdn02.quay.io, and us-docker.pkg.dev
Step 4: Verify platform-specific requirements
If you using one of the following platforms, review further requirements. Otherwise, you are ready to connect your cluster in Manager UI: go to Managed clusters, and click Connect.