Configuring a Proxy via Provisioning CLI

If your cluster is behind a corporate proxy, you will need to configure the K8s cluster and services to use that proxy, for example, to retrieve images or access services over the Internet.

The Provisioning CLI will initially bootstrap the IEM services. The IEM's App Manager can install additional extensions if they are selected in the App Manager UI.

The Provisioning CLI passes the proxy settings to the IEM by adding environment variables to the K8s installation. The App Manager will use these settings and add the same settings to all installed extensions. You can change the settings by editing the K8s resource definition files.

Use the following flags with example values for passing the proxy settings to the services, make sure to mask the no_proxy settings:

--set global.proxy.http_proxy='http://<user>:<password>@<proxy>:<port>'
--set global.proxy.https_proxy='http://<user>:<password>@<proxy>:<port>'
--set global.proxy.no_proxy='.svc\,.svc.cluster.local\,localhost\,127.0.0.1\,10.0.0.0/8\,172.16.0.0/12\,192.168.0.0/16\,POD_IP_RANGE\,SERVICE_IP_RANGE'

no_proxy specifies an exclusion list, but there is no standard way to exclude entire domains or IP ranges. This depends on the component you are using.

no_proxy should be set at least to: "localhost,.svc,.cluster.local,.svc.cluster.local,127.0.0.1,169.254.0.0/16,POD_IP_RANGE,SERVICE_IP_RANGE"