---
title: "Connect a cluster to Calico Cloud"
description: "Connect a Kubernetes cluster to Calico Cloud using the standard install command from the management UI."
product: "Calico Cloud"
version: "v23.0.1"
section: "Install and upgrade"
canonical_url: "https://docs.tigera.io/calico-cloud/get-started/install-cluster"
---

# Connect a cluster to Calico Cloud

You can quickly connect a cluster to Calico Cloud by generating a unique kubectl or Helm command in the web console and running it on your cluster.

## Prerequisites

- You have an paid Calico Cloud account.
- You are signed in to the web console as a user with the **Owner**, **Admin**, or **DevOps** role.
- You have at least one cluster that meets our [system requirements](https://docs.tigera.io/calico-cloud/get-started/system-requirements.md).
- You have kubectl access to the cluster.
- If you're using Helm, you installed Helm 3.0 or later on your workstation.

## Connect a cluster to Calico Cloud with kubectl

1. If your organization uses multiple projects to group managed clusters, click the **Project** menu and select the project you want your cluster to be part of.
2. From the **Managed Clusters** page, click **Connect Cluster**.
3. In the **Connect a Cluster** dialog, enter a **Cluster Name** and select a **Cluster Type**.
4. Optional: If you must install a specific older release, select the Calico Cloud version you want to install. We always recommend the latest version, which is installed by default.
5. Click **Connect** to generate a unique kubectl command. Copy the command.
6. From a terminal, paste and run the command.
7. On the **Managed Clusters** page, you should immediately see your cluster in the list of managed clusters. Monitor the status under **Connection Status**. When the status changes to **Connected**, installation is complete and your cluster is connected to Calico Cloud.

## Connect a cluster to Calico Cloud with Helm

1. If your organization uses multiple projects to group managed clusters, click the **Project** menu and select the project you want your cluster to be part of.

2. From the **Managed Clusters** page, click **Connect Cluster**.

3. In the **Connect a Cluster** dialog, enter a **Cluster Name** and select a **Cluster Type**.

4. Optional: If you must install a specific older release, select the Calico Cloud version you want to install. We always recommend the latest version, which is installed by default.

5. Click **Connect** to generate a unique Helm installation command. Copy the command.

   Example of generated Helm installation command

   ```bash
   helm repo add calico-cloud https://installer.calicocloud.io/charts --force-update && helm upgrade --install calico-cloud-crds calico-cloud/calico-cloud-crds --namespace calico-cloud --create-namespace && helm upgrade --install calico-cloud calico-cloud/calico-cloud --namespace calico-cloud --set apiKey=ryl34elz8:9dav6eoag:ifk1uwruwlgp7vzn7ecijt5zjbf5p9p1il1ag8877ylwjo4muu19wzg2g8x5qa7x --set installer.clusterName=my-cluster --set installer.calicoCloudVersion=v19.1.0
   ```

6. Optional: If you want to enable the Packet Capture or Compliance Reports features, you can append `--set installer.components.packetCaptureAPI.state=Enabled` to the generated Helm command. You can change this option only by reinstalling or upgrading Calico Cloud and changing the values.

   | Feature            | Key                                           | Values                                                                                                                                                                       |
   | ------------------ | --------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
   | Packet Capture     | `installer.components.packetCaptureAPI.state` | `Enabled`, `Disabled` (default\*) \* The default for new clusters is `Disabled`. For upgrades for previously connected clusters, the default will retain the previous state. |
   | Compliance Reports | `installer.components.compliance.enabled`     | `true`, `false` (default)                                                                                                                                                    |

   Example of generated Helm command with user-added parameters

   ```bash
   helm repo add calico-cloud https://installer.calicocloud.io/charts --force-update && helm upgrade --install calico-cloud-crds calico-cloud/calico-cloud-crds --namespace calico-cloud --create-namespace && helm upgrade --install calico-cloud calico-cloud/calico-cloud --namespace calico-cloud --set apiKey=ryl34elz8:9dav6eoag:ifk1uwruwlgp7vzn7ecijt5zjbf5p9p1il1ag8877ylwjo4muu19wzg2g8x5qa7x --set installer.clusterName=my-cluster --set installer.calicoCloudVersion=v19.1.0 \
   --set installer.components.packetCaptureAPI.state=Enabled
   ```

   In this example, the command connects the cluster to Calico Cloud with the Packet Capture feature enabled.

7. From a terminal, paste and run the command.

8. On the **Managed Clusters** page, you should immediately see your cluster in the list of managed clusters. Monitor the status under **Connection Status**. When the status changes to **Connected**, installation is complete and your cluster is connected to Calico Cloud.

## Additional resources

- [Calico Cloud troubleshooting checklist](https://docs.tigera.io/calico-cloud/get-started/checklist.md)
- [Tigera Operator troubleshooting checklist](https://docs.tigera.io/calico-cloud/get-started/operator-checklist.md)