> For the complete documentation index, see [llms.txt](https://docs.kubolabs.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.kubolabs.io/getting-started/kubovisor/cloud-mode.md).

# Cloud mode

Go to your clusters list, click on the « Add » button and select the « Cloud » installation type.

<figure><img src="/files/RKxoQVUc7hB9cHELkmB6" alt=""><figcaption><p>Add cluster button.</p></figcaption></figure>

## :construction\_site: Prepare your cluster

Before going further, you need to prepare your cluster for KuboVisor. This preparation involves the creation of several authorization related resources (RBAC) needed to grant enough permissions for KuboVisor.

To perform the preparation, please choose between:

* using our [automatic install script](/getting-started/kubovisor/cloud-mode/automatic-setup.md) for an easy setup
* following our guided [manual instructions](/getting-started/kubovisor/cloud-mode/manual-setup.md) to get more details

{% hint style="info" %}
Both methods generate a *kubeconfig* file that **you will need in the next steps.**
{% endhint %}

{% hint style="warning" %}
If your cluster is exposed to the internet through a SSH bastion, please make sure to review the documentation on [how to configure your bastion for KuboVisor](/guides/grant-access-to-a-private-network.md).

If your cluster is fully private, you cannot use KuboVisor in cloud mode, [use KuboVisor agent](/getting-started/kubovisor/agent-mode.md) instead.
{% endhint %}

## :heavy\_plus\_sign: Add your cluster

<figure><img src="/files/aErsgovRbZqk9kyRVxAh" alt=""><figcaption><p>Cluster configuration acknowledgement.</p></figcaption></figure>

When your cluster is configured as requested by [previous section](#prepare-your-cluster), you can click on « My cluster is configured ».&#x20;

On the next screen, you will be requested to fill your cluster details:

* **name:** cluster name as displayed in KuboVisor
* **provider:** provider for your cluster, be it a cloud provider or on premise
* **kubeconfig:** file to use to authenticate with your cluster

<figure><img src="/files/wCAWPCZx3Q0F3iOebSEk" alt=""><figcaption><p>Add cluster form (cloud mode).</p></figcaption></figure>

If you have a **private cluster behind a SSH bastion host**, you need to set the following fields in addition to others:

* **bastion host:** IP/DNS name where your bastion is publicly exposed
* **bastion login:** user login to use to authenticate with your bastion
* **bastion SSH key:** SSH private key to use to authenticate with your bastion
* **API endpoint:** Kubernetes API endpoint to use **from inside your network**

<figure><img src="/files/aWJ8uFG2Rs3WGqT0yF1H" alt=""><figcaption><p>Add cluster form (cloud mode behind SSH bastion).</p></figcaption></figure>

You can check the connection to your cluster with the « Check connection » button. To confirm your cluster details click on « Add cluster ».

After your cluster has been added, it will be displayed in the user interface as “disabled” until data is received.

<figure><img src="/files/MBEUblHNtDaIJOWVK8AW" alt=""><figcaption><p>Cluster waiting for data.</p></figcaption></figure>

This process can take up to 5 minutes. If it takes more time than that, please review the [troubleshooting](/getting-started/kubovisor/troubleshooting.md) page. If you can’t resolve the issue by yourself, feel free to contact us via [email](mailto:techsupport@kubolabs.io) or our in-app chat.

## :rocket: Get to know your cluster

When data is available, you’ll see colored indicators regarding your cluster's state, health and security. Go ahead, click on them to display the details!

Elements shown in **red** are issues that should be addressed **as soon as possible**.

While elements shown in **orange** are problems that **should still be addressed**, they don’t threaten your cluster nor your workloads.

If everything is **green**, congratulations! That means your cluster is in very good shape :sunglasses: **Try to keep it this way!**