-
Notifications
You must be signed in to change notification settings - Fork 16
Possible to use a proxy? #16
Comments
@2ZZ : The adapter currently doesn't support configuring an HTTP(S) proxy for outgoing connections. However, it does support overriding the two endpoints that it sends data to (New Relic API endpoints):
Not sure if that helps as your proxy would have to be configured to forward those requests to the New Relic endpoints without the initial request being to those URL. Let me know if that doesn't help. I can see about adding proxy support if not. |
Hi @MrAlias, thanks, I can probably get by doing that while testing but if possible a proxy parameter would be much preferred. |
@2ZZ : did you by chance try setting the |
I did yes, I set http_proxy, https_proxy and the same in upper case. |
Interesting. I'm going to see if I can reproduce locally to dig further into this. |
@2ZZ : I was able to reproduce the SIGTERM locally with your env settings. Looks like the healthcheck is failing based on the generic endpoint it is configured to use:
Using the following config got around the SIGTERM:
The important change being the readiness and liveness probe addresses. They used to just be I don't have a valid proxy to check against to validate that part now works. Are you able to test this out? |
That is looking better thanks
Is it possible to increase logging so I know which URL is returning it? I may need to whitelist it in the proxy. |
@2ZZ : you can set the log verbosity as an arg to the adapter command:
Probably something we should expose via a Helm value... |
Nevermind, it is something we already support: https://github.com/newrelic/newrelic-istio-adapter/blob/master/helm-charts/values.yaml#L33-L35 Just need to updated the docs about it. |
thanks
It was due to an incorrect API key
all working now |
Include configuration values to define an HTTP(S) proxy and endpoints to not proxy. Fixes newrelic#16
Hi,
Is it possible to deploy this app with an outbound proxy where direct access is not permitted?
I tried to pass the proxy as an environment variable
But the pod never becomes ready
The text was updated successfully, but these errors were encountered: