NetBackup™ Marketplace Deployment on Amazon Elastic Kubernetes Service (EKS) Cluster
- Introduction to NetBackup Marketplace deployment on EKS Cluster
- Deployment with the AWS Marketplace offer
- Prerequisites for deployment
- Policies required in creating IAM roles for new and existing clusters
- Before you begin the deployment
- Subscribe to the AWS Marketplace
- Deploy NetBackup powered by Cloud Scale Technology on AWS
- Configuration Parameters
- Basics
- Cluster Configuration
- Primary server Node group Configuration
- Media Server Node group Configuration
- Storage server Node group Configuration
- Snapshot Manager Data Plane node group Configuration
- Primary server details
- Media server details
- Storage server details
- Snapshot Manager details
- Other Configuration
- Accessing the NetBackup
- Cleanup the environment
Cluster Configuration
In the Cluster Configuration section, provide the following details as required:
Table: Cluster configuration parameters
Parameters | Description |
|---|---|
Create a new EKS cluster | Select 'Yes' to create a new EKS cluster, or select 'No' to provide an existing EKS cluster. Cluster name can contain only alphanumeric characters (case-sensitive) and hyphens. It must start with an alphabetic character and can't be longer than 100 characters. |
Virtual network | Select a VPC for the EKS cluster subnet and the application Load Balancer subnet. We do not support creation of VPC as part of deployment. Make sure you select the same network as that of the cluster vNet. |
Kubernetes cluster name | Name for the EKS cluster. This must be unique within the region. Cluster name can contain only alphanumeric characters (case-sensitive) and hyphens. It must start with an alphabetic character and can't be longer than 100 characters. |
Configure access to the Kubernetes API server endpoint from outside of your VPC | Select True to configure access to the Kubernetes API server endpoint from outside of your VPC. Select False to if you want to limit access to the Kubernetes API server endpoint within your VPC. |
Subnet 1 for EKS Cluster | Select a subnet from the virtual network. Subnet1 and Subnet2 must be in different availability zone. |
Subnet 2 for EKS Cluster | Select a subnet from the virtual network. Subnet1 and Subnet2 must be in different availability zone. This subnet will be used to create node groups. |
Subnet for Load Balancer | Select a subnet from the virtual network. Load balancer and Node Group subnets must be in same Availability Zone. |
Additional security group | Specify additional security group for your Amazon EKS Cluster. Ensure that your additional security group of cluster contains inbound rule which allows communication within VPC. |
CIDR block to assign Kubernetes service IP addresses from for your Amazon EKS cluster | The CIDR block to assign Kubernetes service IP addresses from. Must be in valid CIDR notation. For example : 10.0.0.0/16 |
Cluster service role | Select the IAM role to allow the Kubernetes control plane to manage AWS resources on your behalf. This property cannot be changed after the cluster is created. To create a new role, refer to pt.2 from See Prerequisites for deployment . topic. For more information on IAM role, refer the Amazon EKS Cluster IAM role and Amazon EKS Node IAM role . |
IAM role required to access EKS Cluster from EC2 | Required in case of new cluster creation only. Specify the Amazon Resource Name (ARN) of the IAM role, required to access EKS Cluster from EC2. It must be different from the role mentioned above. Policies required in creating IAM roles for new and existing clusters |
Cluster security group created by EKS | Required in case of existing cluster only (dummy value needs to be provided in case of new cluster) Specify security group created for cluster by Amazon EKS. |