Nextgen Gateway FAQs

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

Example

After disabling squid-proxy

How to configure the SNMP V3 trap credential in NextGen gateway

Refer the Document to configure the SNMP V3 trap credential in NextGen gateway: