The proxy server configuration is available only for Multi-Site Orchestrator deployments in Cisco Application Service Engine.
If your cluster is deployed in a Docker swarm, this option will not be available in the GUI.
In certain deployment scenarios, such as with a combination of on-premises and cloud sites and the Orchestrator running inside
a corporate network, the Orchestrator may have to access the internet and the cloud sites through a proxy. You can configure
and enable proxy as described in this section.
When a proxy server is enabled, the Orchestrator will maintain a "no proxy" list of IP addresses and hostnames with which
it will communicate directly bypassing the proxy. This list is a combination of user-specified hosts or domains plus all on-premises
APIC sites currently added to the Orchestrator. Every time the list is updated with a new address, for example if you add
a new site to the Orchestrator, the proxy service is restarted. You can minimize the service restarts by providing a complete
list of your on-premises sites in advance, for example by adding an entire domain to the "no proxy" list, while configuring
the proxy settings.