If you are running on our legacy Docker-based architecture, see legacy guide.
To run Hyperglance behind a proxy please follow these steps:
1) Open for editing the values.yaml used for your deployment. The default location for this is /var/lib/data/hyperglance_helm_charts/values.yaml.
2) Configure the proxy settings.
[Optionally] If your proxy requires a username and password you can set the username and password.
proxy:
enabled: false
existingSecretName:
host:
port: 3128
user:
pass:
3) When running in AWS we must explicitly exclude the AWS metadata service which runs on the link-local IP 169.254.169.254 from being proxied. This is set as a default in the values.yaml under hyperglanceEnvVars.NON_PROXY_HOSTS. If it is missing from your values.yaml, please add it in.
hyperglanceEnvVars:
NON_PROXY_HOSTS: 'localhost|127.*|[::1]|169.254.169.254'
4) Save the file
6) Restart services:
sudo hg apply-config
Wait a few minutes for Hyperglance start-up and begin collecting data.
If you don't wish to bake your credentials into the values.yaml, you may also reference an existing secret. Further details can be found on our public helm chart repo.
If it is not working as expected then checking the logs may indicate any configuration errors or connectivity issues.
