You can configure an outbound HTTP or HTTPS proxy if your organization mandates the use of a proxy. Clients are configured to send requests to a proxy. The information in this section does not apply to an environment which either has no proxy or which uses an implicit proxy.

Cluster Control Manager configuration

You can configure the outbound proxy in one of the following ways:

• When deploying the Cluster Control Manager OVF by populating the HTTP(S) Proxy Settings section.

• Using the ccmNetSetup command on Cluster Control Manager.

The proxy exclusion list contains addresses with which Cluster Control Manager does not communicate through the proxy. If an HTTP or HTTPS proxy is configured, the proxy exclusion list includes localhost,127.0.0.0/8 by default. As part of the cluster installation, the exclusion list is automatically populated with the Cluster Control Manager, vCenter, cluster FQDN, keepalived virtual IP address, and Kubernetes master host virtual IP address.

The format of the destination address can include an IP address prefix (1.2.3.4), a domain name, or a special DNS label (*). Note the following:

• A domain name can match other names and subdomains.

  For example, with the domains foo.example.com and example.com, example.com matches both the example.com and foo.example.com domains. However, .example.com only matches foo.example.com.

• A single asterisk (*) indicates that no proxying is needed.

• You can include a port number with IP address prefixes and domain names.

  An example of an IP address prefix with a port number is 1.2.3.4:80, and an example of a domain name with a port number is foo.example.com:80.