HTTP proxy configuration

Kong Operator is built with Go and respects the standard proxy environment variables defined by Go’s ProxyFromEnvironment. This allows you to route the KO’s outbound HTTP(S) traffic through a corporate proxy or forward proxy.

Use the following environment variables to configure the proxying:

The lowercase variants (http_proxy, https_proxy, no_proxy) are also supported. If both uppercase and lowercase variants are set, the uppercase variant takes precedence.

The NO_PROXY variable accepts a comma-separated list of entries. Each entry can be:

• A hostname (e.g. example.com) — matches that host exactly.
• A domain with a leading dot (e.g. .example.com) — matches the domain and all subdomains.
• An IP address (e.g. 10.0.0.1).
• A CIDR range (e.g. 10.0.0.0/8).
• * — bypasses the proxy for all requests.

Set the environment variables through Helm values:

customEnv:
  HTTP_PROXY: "http://proxy.example.com:3128"
  HTTPS_PROXY: "http://proxy.example.com:3128"
  NO_PROXY: "10.0.0.0/8,127.0.0.1,localhost,.svc,.cluster.local"

Make sure to include Kubernetes internal addresses (such as .svc and .cluster.local) in NO_PROXY so that in-cluster communication is not routed through the proxy.