Clusters

In the Clusters page, you can view, add, edit, and remove Kubernetes clusters. From the menu bar, go to Configuration > Clusters in the General section.

Adding a cluster

Take the following steps to add a cluster in your CloudCasa account:

1. Click Add cluster + to open the Add cluster pane.

2. Fill in the following fields:

   Name

   Enter a name of the cluster.

   Description (optional)

   Enter description for the cluster.

   Advanced options ► Add tags (optional)

   Enter the key-value pairs for the tags of the cluster. For example, team:marketing.

   Advanced options ► Default backup destination for cluster (optional)

   Select either one of the following options:

   • Use global default

   • CloudCasa Storage

   • My Storage

   See also

   See the following topics for details about the storage:

   • Settings

   • Storage

   Click Save.

   

3. In the next page of the Add cluster pane, ensure that you can see basic information of the new cluster and the status is showing REGISTERED. See the kubectl command that installs a light weight agent on the cluster; copy this command and run it on a host where kubeconfig is set up to connect to the cluster being registered.

   Click OK to close the Add cluster pane. Ensure that you can see the new cluster in the list.

   

Cluster connectivity

The CloudCasa agent connects out to the CloudCasa service at the endpoint agent.cloudcasa.io:443, and all control traffic travels on this connection.

See also

See Firewalls for details about network connections required by CloudCasa.

If your cluster is running in a private network and has no access to the public Internet, it will not be able to connect to the above endpoint. However, CloudCasa supports connectivity via AWS PrivateLink. So if your cluster is running in an AWS VPC, you will be able to use AWS PrivateLink to set up a private connection to the CloudCasa service. If you are interested in making use of this feature, contact CloudCasa support.

If your cluster is running in other cloud providers such as Azure or GCP, it may still be possible to set up a private connection. Contact CloudCasa support for further details.

Note PrivateLink connections to CloudCasa are only available with paid service plans.

Removing a cluster

In the cluster list, click Remove and follow the instructions.

Attention

After removing the cluster, manually remove any PV snapshots that were created by CloudCasa as part of the cluster’s Snapshot backups.

After the cluster is removed from CloudCasa, run the following commands on the cluster node:

$ kubectl delete namespace/cloudcasa-io clusterrolebinding/cloudcasa-io

$ kubectl delete crds -l component=kubeagent-backup-helper

Ensure that you do not see the cluster in the list.