NextGen Gateways

Introduction

OpsRamp NextGen gateway builds on our battle tested and proven current gateway to address the growing demands around high-availability, scalability, ease-of-onboarding and the need to simplify the overall discovery and monitoring of our customers' ever growing Hybrid Cloud environments.

The cloud-native and microservices based NextGen gateway leverages the industry standard Kubernetes platform to deliver on it’s goals and as such is the first in the ITOM space to be bringing the power, flexibility and operational familiarity of Kubernetes eco-system to hybrid cloud discovery and monitoring.

With NextGen gateway we are also consolidating our collector technologies - both agent and agent less, via a lightweight bootstrap tool which simplifies collector onboarding into various target environments - bare-metal, virtualized, containerized and Kubernetes environments. This collector bootstrap, a small program, can be downloaded and executed on various OS platforms. Once executed, it will then deploy, register the specific collector type (agent, or a gateway) into the cloud platform and has the ability to start discovering and monitoring your hybrid environments automatically.

Limitation

At this point, the NextGen gateway does not support the scalability feature, so multiple replicas are not supported. This will be available in future releases.

The NextGen gateway collector is currently deployed in the following three ways:

FAQ’s

How do I add proxy settings to Node?

Step-1: Add the proxy settings to /etc/environments.

HTTP_PROXY=
HTTPS_PROXY=
NO_PROXY=localhost,127.0.0.1,10.42.0.1/8,10.43.0.1/8,<NODE_IPs>

Step-2: Login again with the same user for the proxy settings to function properly. Step-3: Now, install the k3s.
Step-4: The proxy settings listed above will also be added to /etc/systemd/system/k3s.service.env

How do I change proxy settings at the node level after installing k3s?

Step-1: Edit the proxy settings in /etc/systemd/system/k3s.service.env
Step-2: Now, use the following command to restart the k3s service:

systemctl restart k3s

Note

The above configurations are only for node level proxy settings such as pulling helm charts etc. and will not be reflected in containers.

How can I enable “squid-proxy” after registering the NextGen gateway?

Use the following command to enable squid-proxy:

helm upgrade nextgen-gw oci://us-docker.pkg.dev/opsramp-registry/gateway-cluster-charts/nextgen-gw --version 1.6.0 --set squidproxy=enable --reuse-values

Example

After enabling squid-proxy

How can I disable “squid-proxy” after registering the NextGen gateway?

Use the following command to disable squid-proxy:

helm upgrade nextgen-gw oci://us-docker.pkg.dev/opsramp-registry/gateway-cluster-charts/nextgen-gw --version 1.6.0 --set squidproxy=disable --reuse-values