> Documentation > End User Access > Command Center > Kubernetes > Getting Started

Hardware Specifications for the Access Node

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

The hardware specifications for access nodes are as follows:

  • 2 x vCPUs

  • 4 GB RAM

  • 100 MB of local disk space for the Commvault software

  • 1GbE network interface for backup data

Automatic Load Balancing Across Access Nodes

To manage your growing Kubernetes data, Commvault does not recommend increasing the hardware specifications of your access node. Instead, you can add additional access nodes (with identical hardware specifications) to your Kubernetes hypervisor. The Commvault software performs automatic load balancing across the access nodes.

External Connectivity

  • Optional: Access to Docker Hub (https://hub.docker.com) from the Kubernetes cluster, to download the following docker image: https://hub.docker.com/_/centos.

    Note

    Commvault downloads and uses the centos:8 image to create a temporary container during backups.

Air-Gapped Clusters

By default, the Kubernetes agent downloads the image from the Docker Hub (https://hub.docker.com) to run backups and restores. For air-gapped clusters, create the following additional settings to run backups and restores.

  1. Verify that the centos:8 image is available on the private registry.

    The private registry is used only to create intermittent Commvault pods that are used for backups and restores.

  2. To the access node, add the additional settings as follows:

    Additional setting

    Category

    Type

    Value

    sK8sUseImageRegistry

    VirtualServer

    String

    Custom

    K8sImageRegistryUrl

    VirtualServer

    String

    A private registry URL along with port, if any.

    For example, cvregistry.cv.com:5000

    sK8sImageSecretName

    VirtualServer

    String

    The ImagePullSecret for container, if any, to authenticate with the image registry. For example, regcred.

    sK8sWorkerImageName

    VirtualServer

    String

    The image for the worker pod type. For example, debian:stretch-slim.

    By default, centos:8 image is used.

Next time when you run a backup job, the intermittent CV pods use the centos:8 image from the registry provided in the sK8sImageRegistryUrl additional setting.

Loading...