Hardware Specifications for the Access Node for Kubernetes


You must have at least one access node for Kubernetes. For faster backups and restores, you can add more access nodes.

Hard Drive


Space required


100 MB



Network interface for backup data


Memory (RAM)

4 GB.


Scale the Kubernetes access nodes horizontally for consistent scaling and performance.

For resilience scaling, add an additional access node. If the recovery point objective (RPO) cannot be met within the backup window, add additional access nodes.

Generally, approximately 32TB data can be transferred in a standard 8 hour backup window, on a 10GbE network configuration.

In addition, the read speed from disks, the network throughput from worker nodes, and the network throughput on your access nodes affect the amount of data transferred in the backup window.

Operating System


  • Red Hat Linux 7.x, 8.x: Commvault supports all 7.x and 8.x GA releases. For information, see Red Hat Enterprise Linux Release Dates on the Red Hat customer portal.

  • CentOS 7.x, 8.x: Commvault supports all actively supported CentOS releases. For information, see CentOS Manual on the CentOS website.


  • Microsoft Windows Server 2019 Editions

  • Microsoft Windows Server 2016 Editions

Automatic Load Balancing Across Access Nodes

To manage your growing Kubernetes data, instead of increasing the hardware specifications of your access node, add more access nodes (with identical hardware specifications) to your Kubernetes hypervisor.

The Commvault software performs automatic load balancing across the access nodes.

Network and Firewall

Network Interface

1GbE network interface for backup data.

Port That Must Be Open

If a firewall exists between the Kubernetes access nodes and the Kubernetes cluster, the following port must be open:

TCP: API_server_port_number incoming to your Kubernetes master server from the access nodes

Note: The default port of kube-apiserver is 443. To validate your cluster, run the following command on your API server:grep server /etc/kubernetes/admin.conf


The Commvault software requires a Layer 3 network connection between the access node and the Kubernetes API server endpoint on port 443 (or equivalent TLS-SSL port in the /etc/kubernetes/admin.conf file on the admin server).

External Connectivity

If you want access to the Docker Hub (https://hub.docker.com) from the Kubernetes cluster, download the following docker image:


Note: Commvault downloads and uses the debian:stretch-slim image to create a temporary container during backups.


Third-party maintenance (minor) releases or feature releases that are supported by the Commvault software may not be listed in our System Requirements. When possible, Commvault provides information on any known issues related to these minor releases or feature releases. In some cases, these minor releases or feature releases affect how the Commvault software works. Commvault software may experience changes in functionality as the result of the third-party minor release or feature releases. These changes are beyond the control of Commvault. Platforms that are supported in the current version of Commvault software may not be supported in earlier versions of the software. Contact your software provider to ensure that third-party minor releases or feature releases are compatible with the Commvault software.

Additional considerations regarding minimum requirements and End-of-Life policies from third-party vendors also apply.