Search <book_title>...

Veritas NetBackup™ CloudPoint Install and Upgrade Guide

Last Published: 2022-03-28

Product(s): NetBackup & Alta Data Protection (10.0)

Preparing to install the extension on a managed Kubernetes cluster (EKS) in AWS

The CloudPoint cloud-based extension can be deployed on a managed Kubernetes cluster in AWS for scaling the capacity of the CloudPoint host to service a large number of requests concurrently.

Overview

Your AWS 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: AmazonEKSClusterPolicy AmazonEKSWorkerNodePolicy AmazonEC2ContainerRegistryReadOnly AmazonEKS_CNI_Policy AmazonEKSServicePolicy
For supported Kubernetes versions, refer to the CloudPoint Hardware Compatibility List (HCL).
Use an existing AWS Elastic Container Registry or create a new one, and ensure that the EKS has access to pull images from the elastic container registry.
A dedicated nodepool for CloudPoint workloads needs to be created in AWS managed Kubernetes cluster. The nodepool uses AWS autoscaling group feature which 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 AWS container registry.

Prepare the host and the managed Kubernetes cluster in AWS

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.
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 AWS environment.
- Install AWS CLI.
  https://docs.aws.amazon.com/cli/latest/userguide/cli-chap-install.html
- Install Kubernetes CLI
  https://docs.aws.amazon.com/eks/latest/userguide/install-kubectl.html
- Create an AWS Container Registry or use the existing one if available, to which the CloudPoint images will be pushed (uploaded). Configure the minimum and maximum nodes as per the requirement.
  See AWS documentation https://aws.amazon.com/ecr/getting-started/.
- Create the OIDC provider for the AWS EKS cluster.
  See https://docs.aws.amazon.com/eks/latest/userguide/enable-iam-roles-for-service-accounts.html.
- Create an IAM service account for the AWS EKS cluster.
  See https://docs.aws.amazon.com/eks/latest/userguide/efs-csi.html.
- If an IAM role needs an access to the EKS cluster, run the following command from the system that already has access to the EKS cluster:
  kubectl edit -n kube-system configmap/aws-auth
  See https://docs.aws.amazon.com/eks/latest/userguide/add-user-role.html
- Install Amazon EFS driver .
  See https://docs.aws.amazon.com/eks/latest/userguide/efs-csi.html.
- Login to the AWS environment to access the Kubernetes cluster by running this command on AWS CLI:
  # aws eks --region <region_name> update-kubeconfig --name <cluster_name>
Create a storage class.
See https://docs.aws.amazon.com/eks/latest/userguide/efs-csi.html
Create a namespace for CloudPoint from the command line on host system:
# kubectl create namespace cloudpoint-system
Then create a new or use an existing managed Kubernetes cluster in AWS, and add a new node pool dedicated for CloudPoint use. Configure Autoscaling as per your requirement.

See Downloading the CloudPoint extension.

See Installing the CloudPoint extension on Azure (AKS).

See Installing the CloudPoint extension on AWS (EKS).