Configure HTTP Proxy

Configure HTTP proxy for the Konvoy cluster

For some production environments, direct access to the Internet could be blocked. In those environments, they typically only allow Internet access through HTTP or HTTPS proxies.

Konvoy can be configured to use HTTP/HTTPS proxy for Internet access. This applies to all Kubernetes components, as well as workloads running on top of Kubernetes assuming the workloads understand standard HTTP/HTTPS proxy environment variables:

  • HTTP_PROXY: the HTTP proxy server address.
  • HTTPS_PROXY: the HTTPS proxy server address. (Ansible only supports http:)
  • NO_PROXY: a list of IPs and domain names that do not subject to proxy settings.

Before you start

Please make sure the proxy server is running and functional. This can be verified using a simple curl command from a node in the cluster. Assume is the HTTP proxy server address.

http_proxy= curl --head

If the proxy is working properly, a 200 OK HTTP response should be received.

Install Konvoy with HTTP/HTTPS proxies

Edit the cluster configuration file cluster.yaml to specify HTTP/HTTPS proxies for the cluster.

kind: ClusterConfiguration
      httpProxy: ""
      httpsProxy: ""
        - "localhost"
        - ""
        - ""
        - "mycluster.icp:8500"

The above example configures the Kubernetes cluster installed by Konvoy to use proxy server for all HTTP traffic and proxy server for all HTTPS traffic, except for those HTTP/HTTPS requests to localhost,, and mycluster.icp:8500.

All the proxy related fields are optional.

The proxy configuration will be applied automatically by Konvoy after you run

konvoy up

Important if the machine where the konvoy binary is being run from requires the HTTP/HTTPS proxy for Internet access, you must set the same HTTP_PROXY, HTTPS_PROXY and NO_PROXY as environment variables before running konvoy. These proxy settings will be used by the binary itself (not Kubernetes cluster machines) to download addon configurations over the Internet.