Terminating Gateway in kubernetes behind forward proxy

I am deploying Consul in kubernetes behind a service that must route traffic through a proxy server to the public internet. How do I configure

  • http_proxy
  • https_proxy
  • no_proxy

Are their special consideration for these valules for consul service names? internal routing domain names? etc.?

Hi, so is the traffic flow:

app → consul connect proxy → terminating gateway → public internet proxy → public internet


And so you want to ensure the terminating gateway sends its traffic through to the public internet proxy rather than directly out to the public internet?

Correct. All traffic must flow through proxy/firewalls to reach the public internet.

I’ve tried adding extraEnvironmentVars: in the helm values to the server and client. However I didn’t see an option for it in terminatingGateway.

I would like to bump this topic.