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-4: The proxy settings listed above will also be added to
/etc/systemd/system/k3s.service.envHow 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 k3sNote
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 
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 
How to configure the SNMP V3 trap credential in NextGen gateway
Follow the below steps to configure the SNMP V3 trap credential in NextGen gateway:
- Create a yaml and pass the snmp_v3 credentials in the below format.
Example:snmp_trap_v3_credentials: |-snmp_trap_v3_credentials: |- key1 key2 key3
Note
- Please ensure that there are two spaces under the “snmp_trap_v3_credentials” and then pass the keys after those spaces, as the spaces are necessary for YAML indentation.
- Refer Configure SNMP v3 Traps for more details on configuring SNMP credentials.
helm upgrade nextgen-gw oci://us-docker.pkg.dev/opsramp-registry/gateway-cluster-charts/nextgen-gw --version <current_helm_chart_version> -f <YamlFileName> -n <NAMESPACE> --reuse-values