Installation Using The NKP Application Catalog

The CloudCasa agent is available for installation from the Nutanix NKP partner application catalog.

Installing the CloudCasa agent

Configure your cluster in CloudCasa, if it hasn’t been configured there already. Obtain the CloudCasa cluster ID.

See also

Adding a Cluster
From the Nutanix Kommander console Applications tab, find the CloudCasa Agent listing and click Enable. In the Workspace Configuration box paste in the following YAML defining the CloudCasa Helm chart options:
```
clusterID: ""

image:
  repository: "cloudcasaAgent.azurecr.io/catalogicsoftware/amds-kagent"
  tag: "3.1.0-prod"

server:
  address: "agent.cloudcasa.io:443"
  skipTLSVerification: false
```
The cluster ID will be different for each cluster which is why it shouldn’t be defined here.
Add a project, using tags or explicit definitions to select the cluster(s) you wish to protect with CloudCasa.

#. From the console Clusters tab, select the cluster you want to install on. find the CloudCasa Agent listing and click Enable.

Enter an ID string such as “cloudcasa” in the Id field.
In the Workspace Configuration box paste in the following YAML defining the CloudCasa Cluster ID, replacing <cluster-id> with the ID for your cluster from CloudCasa:
```
clusterID: "<cluster-id>"
```
Click Enable to install and configure the CloudCasa agent.
After a few minutes, the CloudCasa Agent will show as “Enabled” in the management UI. You can verify the status by viewing the list of enabled applications for each cluster. In the CloudCasa UI, the status of the cluster should change to “Active”.

Using an alternate image repository

The agent manager container can be installed from an alternate repository by setting values for image.repository and image.tag.

Note that the alternate repository will also need to be set for the cluster in CloudCasa so that all agent containers will be loaded from it. This can be done using the Private container registry for agent field under Advanced options in the Add cluster dialog. See Adding a Cluster for more information.

If the registry you are using requires authentication, you can define a Kubernetes secret with the authentication information and reference it by setting a value for imagePullSecret. See the Kubernetes Docs for more information. Note that the secret must be created in the cloudcasa-io namespace, so you may need to create the namespace first. Also note that when uninstalling the agent, you may need to delete the cloudcasa-io namespace manually after the uninstall with kubectl delete namespace cloudcasa-io.

Finally, the secret name will also need to be set in CloudCasa for the cluster, so that it will be used for all agent containers. This can be done using the Image pull secret field under Advanced options in the Add cluster dialog. See Adding a Cluster for more information.

Configuring the agent for use with self-hosted CloudCasa

When installing the agent for use with self-hosted CloudCasa, you must configure the correct image repository and tag for the self-hosted agent containers as described above. You must also set the server.address option to point to your CloudCasa server. See the CloudCasa Self-hosted Administrator’s Guide or contact your administrator for more information.