Veritas NetBackup™ CloudPoint Install and Upgrade Guide

Your Azure managed Kubernetes cluster should already be deployed with appropriate network and configuration settings, and with specific roles. The cluster must be able to communicate with CloudPoint.

The required roles are: Azure Kubernetes Service RBAC Writer, AcrPush, Azure Kubernetes Service Cluster User Role

For supported Kubernetes versions, refer to the CloudPoint Hardware Compatibility List (HCL).

Use an existing Azure Container Registry or create a new one, and ensure that the managed Kubernetes cluster has access to pull images from the container registry

A dedicated nodepool for CloudPoint workloads needs to be created with manual scaling or 'Autoscaling' enabled in the Azure managed Kubernetes cluster. The autoscaling feature allows your nodepool to scale dynamically by provisioning and de-provisioning the nodes as required automatically.

CloudPoint extension images (flexsnap-cloudpoint, flexsnap-listener, flexsnap-workflow, flexsnap-fluentd, flexsnap-datamover) need to be uploaded to the Azure container registry.

Choose the CloudPoint image supported on Ubuntu or RHEL system that meets the CloudPoint installation requirements and create a host.

See Creating an instance or preparing the host to install CloudPoint.

Verify that the port 5671 is open on the main CloudPoint host.

See Verifying that specific ports are open on the instance or physical host.

The public IP of the virtual machine scale set via which the node pool is configured has to be allowed to communicate through port 22, on the workloads being protected.

Install a Docker or Podman container platform on the host and start the container service.

See Table: Installing container platform.

Prepare the CloudPoint host to access Kubernetes cluster within your Azure environment.

Ensure to create an Azure Container Registry or use the existing one if available, to which the CloudPoint images will be pushed (uploaded). See Azure documentation:

https://docs.microsoft.com/en-in/azure/container-registry/container-registry-get-started-portal

https://docs.microsoft.com/en-in/azure/container-registry/container-registry-get-started-azure-cli

To run the kubectl and container registry commands from the host system, assign the following role permissions to your VM and cluster. You can assign a 'Contributor', 'Owner', or any custom role that grants full access to manage all resources.

Create a storage account in the same subscription and region your Kubernetes cluster is in, and create a file share into it. (Follow the default settings by Azure.)

https://docs.microsoft.com/en-us/azure/storage/files/storage-how-to-create-file-share?tabs=azure-portal

Create a namespace for CloudPoint from the command line on host system:

# kubectl create namespace cloudpoint-system

Create a Kubernetes secret to access the file share. You will need to provide this secret while configuring the CloudPoint extension.

# kubectl create secret generic <secret_name> --namespace cloudpoint-system --from-literal=azurestorageaccountname=<storage_account_name> --from-literal=azurestorageaccountkey=<storage_account_key>

Pass the following parameters in the command:

Example:

# kubectl create secret generic mysecret --namespace cloudpoint-system --from-literal=azurestorageaccountname=mystorage --from-literal=azurestorageaccountkey=IusI10S9w6n1Ve4N31pFCaWNCWWWPGMw0WzDQT....

Then create a new or use an existing managed Kubernetes cluster in Azure, and add a new node pool dedicated for CloudPoint use. Configure Autoscaling as per your requirement.

Ensure that Azure plug-in is configured.

See Microsoft Azure plug-in configuration notes.