NetBackup™ Deployment Guide for Kubernetes Clusters

• Taints and tolerations allows you to mark (taint) a node so that no pods can schedule onto it unless a pod explicitly tolerates the taint. Marking nodes instead of pods (as in node affinity/anti-affinity) is particularly useful for situations where most pods in the cluster must avoid scheduling onto the node.

  To use this functionality, user must create the node pool/node group with the following detail:

  • Add a label with certain key value. For example key = nbpool, value = nbnodes

  • Add a taint with the same key and value which is used for label in above step with effect as NoSchedule.

    For example, key = nbpool, value = nbnodes, effect = NoSchedule

• Install Cert-Manager. You can use the following command to install the Cert-Manager:

  $ kubectl apply -f https://github.com/jetstack/cert-manager/releases/download/v1.6.0/cert-manager.yaml

  For details, see https://cert-manager.io/docs/installation/

• A workstation or VM running Linux with the following:

  • Configure kubectl to access the cluster.

  • Install Azure/AWS CLI to access Azure/AWS resources.

  • Configure docker to be able to push images to the container registry.

  • Free space of approximately 8.5GB on the location where you copy and extract the product installation TAR package file. If using docker locally, there should be approximately 8GB available on the /var/lib/docker location so that the images can be loaded to the docker cache, before being pushed to the container registry.

AKS-specific

• A Kubernetes cluster in Azure Kubernetes Service in AKS with multiple nodes. Using separate node pool is recommended for the NetBackup servers, MSDP Scaleout deployments and for different media server objects. It is required to have separate node pool for Snapshot Manager data plane.

• Taints are set on the node pool while creating the node pool in the cluster. Tolerations are set on the pods.

• Define storage class of AzureFiles and Azure managed disks for primary and Azure managed disks for media and MSDPX.

• Enable AKS Uptime SLA. AKS Uptime SLA is recommended for a better resiliency. For information about AKS Uptime SLA and to enable it, see Azure Kubernetes Service (AKS) Uptime SLA.

• Access to a container registry that the Kubernetes cluster can access, like an Azure Kubernetes Service Container Registry.

EKS-specific

• A Kubernetes cluster in Amazon Elastic Kubernetes Service in EKS with multiple nodes. Using separate node group is recommended for the NetBackup servers, MSDP Scaleout deployments and for different media server objects. It is required to have separate node pool for Snapshot Manager data plane.

• Taints are set on the node group while creating the node group in the cluster. Tolerations are set on the pods.

• Access to a container registry that the Kubernetes cluster can access, like an Amazon Elastic Kubernetes Service Container Registry.

• AWS network load balancer controller add-on must be installed for using network load balancer capabilities.

• AWS EFS-CSI driver must be installed for statically provisioning the PV or PVC in EFS for primary server.