Setting Up a Container as an Access Node

You can use a Kubernetes container as the access node for your Kubernetes backups in Commvault.

Before You Begin

• Set up Helm in your Kubernetes environment. For more information, Helm.

  For information on how to add the repo, view the charts, see Installing Commvault Packages in Kubernetes Using Helm.

• The Kubernetes cluster must meet the following network requirements:

  • The access node container must have network connectivity to the Commvault CommServe server and MediaAgent components.

  • The following ports must be open for communication:

    • 8400-8403: Used for communication between the access node and CommServe server.

    • 443: For HTTPS communication with the Kubernetes API server.

  • The DNS resolution must be configured correctly for all components in the environment.

Procedure

1. To install the config chart, run the following command:

   helm upgrade --install config commvault/config --set csOrGatewayHostName=cs.commvault.svc.cluster.local --set secret.user=installuser --set secret.password=password --namespace commvault

   The config chart contains the config map for all of the Commvault component chart installs. You must always install the config chart before a new chart installation.

   Note

   By default, the config chart deploys a container with cvpatcher service. This service facilitates the automatic upgrading of container clients whenever an installation upgrade job is triggered from the console.

   If you do not want to deploy the cvpatcher service, then add the following parameter to the helm upgrade command: --set cvpatcher=false

2. To install the access node chart, run the following command:

   helm upgrade --install accessnode commvault/accessnode --set clientName=accessnode --set global.image.tag=tagValue --namespace commvault

CHANGE_STATUS: CHANGES_MADE - Added network requirements and port details to the "Before You Begin" section.