This section describes how to install nextgen gateway through Helm based deployment.
Note
If you are using an ISO/OVA that is not provided by OpsRamp, please be aware that OpsRamp cannot assist with the setup of Kubernetes or address any security-related issues associated with Kubernetes.Prerequisites
- Helm 3.8.2 or higher
- Kubernetes (K3S or K8S) - 1.25.x or higher
- 8 GB Memory
- 50 GB Disk
- 4 Core of CPU
- AMD64/ARM64 Arch
- Configure the default storage class and CSI plugin in the Kubernetes cluster.
- When deploying in AWS EKS and using the EFS-based storage class, ensure that both UID and GID are set to 70.
- If you have a multi-node Kubernetes cluster, use an external load balancer service like MetalLB to support multi-node cluster.
- To whitelist NextGen Gateway IPs, refer to the documentation.
Deployment Process
Deploy Helm Chart with Basic Options
Follow the below command to install gateway using helm chart without any additional option.
Deploy Helm Chart with Advanced Options
Deploy the Helm chart with advanced options for installing the NextGen Gateway, including settings for ThirdPartyApp, storage class name, memory limits for the vprobe container, proxy details, nativebridge container, Squid Proxy container, and postgres container.
- Create a yaml file with the following data.
- Update all the required values in the yaml file.
- Install gateway helm chart using the following command.
Note
- If namespace is not passed it will use the default namespace.
- While installing the nextgen gateway, the release name should be nextgen-gw.
Check for Successful Gateway Registration
Use the following command to make sure
nextgen-gw-0
pod status is running.Once the Helm deployment is successful, navigate to Setup > Resource > Management Profile to check if the gateway is registered successfully.
Gateway connection status:
