You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I would like to use this in a corporate environment, but for some reason, the container proxies the request to our internal security proxy and doesn't address the thanos query endpoint directly. I don't know why it is using the security proxy, because I actually specified the upstream as http://thanos-query.thanos.svc.cluster.local:9090.
I also tried to set the environment variables no_proxy, NO_PROXY, http_proxy, HTTP_PROXY, https_proxy and HTTPS_PROXY with no success.
Do you have any idea how to fix this?
The text was updated successfully, but these errors were encountered:
Hmm, I'm quite surprised that prom-label-proxy didn't honor the proxy env variables because it doesn't specify any Transport meaning that it uses [http.DefaultTransport](https://pkg.go.dev/net/[email protected]#DefaultTransport:
It uses HTTP proxies as directed by the environment variables HTTP_PROXY, HTTPS_PROXY and NO_PROXY (or the lowercase versions thereof).
Hello,
I would like to use this in a corporate environment, but for some reason, the container proxies the request to our internal security proxy and doesn't address the thanos query endpoint directly. I don't know why it is using the security proxy, because I actually specified the upstream as
http://thanos-query.thanos.svc.cluster.local:9090
.I also tried to set the environment variables
no_proxy
,NO_PROXY
,http_proxy
,HTTP_PROXY
,https_proxy
andHTTPS_PROXY
with no success.Do you have any idea how to fix this?
The text was updated successfully, but these errors were encountered: