This page outlines the prerequisites for deploying the NextGen Gateway on cloud-managed Kubernetes platforms, including Azure Kubernetes Service (AKS), Amazon Elastic Kubernetes Service (EKS), and Google Kubernetes Engine (GKE).

1. System & Kubernetes Requirements

Before proceeding with the Gateway installation, ensure your system and Kubernetes environment meet the minimum supported requirements.

System Requirements

  • For detailed Network (Inbound and Outbound) and Resource requirements refer to the Prerequisites page.

Kubernetes Cluster Requirements

  • Kubernetes Version: 1.25.x or higher
    • Ensure the cluster is up and running, with access configured via kubectl.
  • Node Configuration: If you are configuring the Gateway for high availability, use a minimum of three worker nodes (recommended: 4 vCPUs and 8 GB RAM per node). For single‑node deployments, apply the same resource configuration to the single node.
  • Network Policies: Enabled, if your organization uses them for security purposes.
  • Load Balancer: A Load Balancer should be configured for SNMP traps, Syslogs and Squid for Agent Proxy connectivity
  • Storage Class & CSI Plugin: To ensure persistent storage for the Gateway, configure a default StorageClass and CSI (Container Storage Interface) plugin in your Kubernetes cluster.

Helm Requirements

  • Helm Version: 3.8.2 or higher
    • Helm is required for managing Kubernetes charts during the Gateway deployment. Install Helm on the local system from which deployment commands will be executed. For more details on installation and usage, refer to the official Helm documentation (https://helm.sh).

2. Proxy Server Configuration (Optional)

If your organization routes outbound traffic through a proxy for security or compliance reasons:

  • Configure proxy settings on the Kubernetes nodes where the Gateway will be deployed.
  • This ensures that all outbound traffic, including Gateway registration and communication with OpsRamp Cloud, routes through the proxy.
  • For detailed instructions on setting up proxy configurations, see the Proxy Configuration page.