Configuring Proxy Settings

The cluster should have no access to the Internet and proxy settings (http_proxy, https_proxy and no_proxy) should not be set. However, if you need an Internet connection and you already specified a proxy server for http and https connection, then you must correctly configure no_proxy.

 

No Proxy Definitions

If you have the http_proxy or https_proxy set, then the no_proxy definitions must contain at least the following values:

no_proxy=localhost, 127.0.0.1, <all Master and Worker cluster node IP addresses>,<all Master and Worker cluster node FQDNs>,<HA virtual IP Address>,<FQDN for the HA Virtual IP address>
Incorrect configuration of proxy settings is a common installation issue. To verify that proxy settings are configured properly, on all master and worker nodes, run the following command and ensure the output corresponds to the recommendations.

echo $http_proxy, $https_proxy, $no_proxy

If the firewall is turned off, the install process generates a warning. To avoid this warning, set the OMT install parameter --auto-configure-firewall to true.

Proxy Settings Example

Although the text here is displayed with line breaks due to page limitations, there should be no line breaks in your actual proxy settings.
export http_proxy="http://web-proxy.http_example.net:8080"
export https_proxy="https://web-proxy.http_example.net:8080"
export no_proxy="localhost,127.0.0.1,node1.swinfra.net,10.94.235.231,node2.swinfra.net,10.94.235.232,node3.swinfra.net,10.94.235.233,node3.swinfra.net,10.94.235.233,node4.swinfra.net,10.94.235.234,node5.swinfra.net,10.94.235.235,node6.swinfra.net,10.94.235.236,ha.swinfra.net 10.94.235.200"