search

jaegertracing / helm-charts

Helm Charts for Jaeger backend
Apache License 2.0
266 stars 343 forks source link

handling http proxy when Jaeger agent is configured as sidecar in K8 cluster and collector is in external network #346

Open bnaha opened 2 years ago

bnaha commented 2 years ago

Describe the bug We have solutions deployed as PODS in a K8 cluster. Within the POD the jaeger agent is configured as sidecar container. This agent cannot directly access www. It has to go through a http proxy, However we are unable to find the suitable entries to be made in helm chart for jaeger agent to use proxy.

To Reproduce Steps to reproduce the behavior:

  1. Deploy the jaeger agent as sidecar in a POD using helm chart
  2. Run the flow 3.Connection is not allowed by outbound http proxy

Expected behavior When the jaeger client is deployed in the POD as sidecar and tries to access collector in WWW via http proxy, configured in helm chart, it should be allowed to make outbound connections.

Screenshots If applicable, add screenshots to help explain your problem.

Version (please complete the following information):

What troubleshooting steps did you try? We removed the proxy and it worked. We dont know what entries / configuration needs to be made in the charts to make it go through the http proxy

Additional context Provided above.

yurishkuro commented 2 years ago

Go understands http_proxy env var (1). I don't know much about the helm chart, moving to https://github.com/jaegertracing/helm-charts