LM Container services require a connection to the Internet to transport telemetry and to perform updates. A highly regulated network might employ forward proxies to enable internal services to connect to the internet. For such networks, you can supply the connection details of the HTTP/S Proxy server in the LM Container Helm Chart values file to enable internet access for the LM Container services.
Add the following configuration to the LM Container Helm Chart values file’s global section using the helm upgrade command. For more information, see Installing the LM Container Helm Chart for monitoring Kubernetes Cluster.
Configuring Global Proxy
You can configure proxy at the global level, the configuration settings get applied to all the LM Container services.
global: proxy: url: "" user: "" pass: ""
Configuring a Proxy for Individual Services
You can set a different proxy server configuration for every LM Container component, you can add the proxy server configuration in its respective component’s configuration section in the LM Container Helm Chart configuration file.
Sample for Argus:
# Argus Pod's proxy configuration argus: proxy: url: "" user: "" pass: "" ignoreSSL: false
Sample for Collectorset-Controller
# Collector Pod's proxy configuration (yes, it is nested under the Argus section) collector: proxy: url: "" user: "" pass: "" # Collectorset Controller Pod's proxy configuration collectorset-controller: proxy: url: "" user: "" pass: "" ignoreSSL: false
Note: You must set the flag to true to clear the certificate validations for the HTTP proxy server.