This page provides comprehensive guidance for setting up a High Availability (HA) cluster using the OpsRamp-provided ISO or OVA. Deploying the NextGen Gateway in HA mode improves system resilience, reduces downtime, and ensures continuous availability by distributing workloads across multiple nodes. An HA setup is especially valuable for mission-critical environments where uninterrupted monitoring and alerting are essential.

Prerequisites

Before deploying a High Availability Gateway cluster in your Kubernetes environment, ensure the following requirements are met on each node or virtual machine:

  1. System and Infrastructure Requirements
    • Each node must meet the minimum hardware and software specifications as defined in the Prerequisites document.
    • A minimum of three (3) nodes is recommended for a fully functional HA configuration to support redundancy and load distribution.

  2. IP Address Requirements
    • Allocate one additional static IP address for the Gateway Inbound Load Balancer. This IP handles external traffic, including:
      • SNMP traps
      • Syslog messages
    • (Optional) Reserve one additional static IP if you plan to configure a Squid proxy Inbound Load Balancer, used for routing OpsRamp agent connectivity through a secure proxy layer.
      Refer to the MetalLB IP Range documentation for details on configuring and assigning additional IPs in HA environments.

  3. Network Access and Whitelisting
    To allow the Gateway cluster to communicate with the OpsRamp Cloud platform:
    • Whitelist all required IP addresses and URLs in your firewall, proxy, or network security rules.
    • For a full list of required endpoints, refer to the IP Whitelist documentation.

  4. Gateway Proxy Configuration (Optional)
    If your organization uses a proxy server for outbound traffic:
    • Proxy settings must be properly configured at the each node or environment level to route outbound requests through the proxy.
    • Follow the steps in the Proxy Configuration document to set up and validate proxy access.

  5. Gateway as Proxy Server (Optional)
    • Ensure the Squid proxy service is enabled during the Gateway registration process if OpsRamp agents are connected via OpsRamp gateway proxy.
    • Follow the steps in the Enable Squid Proxy document to set up and validate proxy access.

  6. Node-to-Node Communication and Deployment Location
    To ensure seamless cluster operations and high availability:
    • Unrestricted node-to-node communication must be allowed across all participating nodes. This includes traffic over internal Kubernetes ports, control plane communication, and component synchronization between nodes.
    • It is strongly recommended to deploy all virtual machines (VMs) participating in the HA Gateway cluster within the same data center or availability zone. Co-locating the nodes reduces network latency, avoids inter-zone data transfer issues, and enhances overall cluster performance and stability.

Step 1: Download the NextGen Gateway ISO/OVA

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

You can install the NextGen Gateway as a virtual machine using either the OpsRamp-provided ISO or OVA file, depending on your infrastructure preference. Both methods are fully supported and offer the same functional outcome—it’s up to you to choose the approach that best fits your environment.

Step 3: Change Password

Use the following command to change default password:

passwd gateway-admin

Step 4: Update Hostname and IP Address

Refer to the Update Hostname and IP Address document for step-by-step guidance on configuring the Gateway network settings.

Hostname and IP Configuration Guidelines

Before installing K3s, it is essential to assign a unique hostname and configure the appropriate static IP address for each node. This ensures reliable service discovery, network communication, and node identification within the cluster.

  1. Apply the hostname and IP address changes on every node in the HA cluster.
  2. Each node must have a unique hostname and static IP address.
  3. Consistent configuration across all nodes is critical to maintaining high availability and ensuring smooth inter-node communication.
  4. Each node must have a unique hostname and static IP address.
  5. Consistent configuration across all nodes is critical to maintaining high availability and ensuring smooth inter-node communication.

Step 5: Install Kubernetes

Refer to the Install Kubernetes In Multi-Node Deployment document for step-by-step instructions.

Step 6: Register the Gateway

Refer to the Install Gateway Using OpsRamp Bootstrap Tool document to activate the Gateway collector. This document will guide you through the process of using the bootstrap tool to complete the NextGen Gateway installation.