Installation of NextGen Gateway using ISO

This section describes how to deploy gateway as a virtual machine using ISO image on VMware ESXi Host using vSphere client.

ISO (International Organization for Standardization) is only applicable for the Kubernetes environment and Ubuntu/Linux operating system.

Pre-requisites

To deploy a NextGen cluster in your kubernetes environment, make sure your environment meets these requirements:

• 8 GB Memory
• 50 GB Disk
• 4 Core of CPU
• AMD64 Arch

Step 1: Download the NextGen Gateway ISO

Using the ISO image, you can install the gateway on VMware ESXi Server using VMware vSphere.
To download the gateway follow the below steps:

1. From All Clients, select a client.

2. Go to Setup > Integration and Apps.

3. To find the Collector Profile, either use the search button or select “Other” from the Categories menu.

4. Click + ADD on the GATEWAY COLLECTOR PROFILES page. The ADD GATEWAY COLLECTOR PROFILES page displays all the available gateway collectors.

5. Enter a Profile Name and click the VIRTUAL APPLIANCE (ISO) NEXTGEN tile.

6. Click NEXT.

7. Download the gateway by clicking on the VIRTUAL APPLIANCE (ISO) tile.

8. Once you have downloaded the gateway, proceed to step 2 to install the gateway.

Step 2: Install the NextGen Gateway ISO as a Virtual Machine

Click here to know how to install gateway as a virtual machine using an ISO image.

Step 3: Update Hostname and Install Kubernetes

1. Update the hostname and change the default password.

   Note

   We recommend you to set a unique hostname and change the default password once the gateway is provisioned. This best practice ensures that you have a unique host name and secured password on the network.
   • Use the following command to update the hostname:

         opsramp-collector-start setup updatehostname <new hostname>
         

   • Use the following command to change default password:

         passwd gateway-admin
         

     On successful hostname update, will show the response as below:

     

2. Install the k3s:
   • If you don’t want to use OpsRamp repository and use your own repository (either public or private) for pulling docker images and Helm charts, then follow the below steps:
     • Open the specified yaml file and uncomment the “configs” section.

       vi /var/cgw/asserts_k3s/registries.yaml.template

     • Provide your repository details as follows and ensure proper YAML indentation.
       Example:

       mirrors:
         artifact.registry:
           endpoint:
           - "https://us-docker.pkg.dev"
       configs:
         "{private-repo}":
           auth:
             username: "{user}"
             password: "{password}"

   • Install the k3s using the following command.
     

     opsramp-collector-start setup init

                                               OR
   • Install the k3s with a custom pod/service IP range, use the following command.
     

     opsramp-collector-start setup init --cluster-cidr <cluster-cidr-ip> --service-cidr <service-cide-ip>

     
     On successful k3s installed, will show the response as below:

     

     Check k3s status:

     

Step 4: Register the Gateway Collector

Click here to know how to activate the gateway collector.

Advanced configuration

For advanced configuration and instructions see Collector Bootstrap Tool documentation.