NamespaceManagement_ProxyConfiguration

NamespaceManagement_ProxyConfiguration
NamespaceManagement_ProxyConfiguration

The ProxyConfiguration structure defines proxy configuration to be used by the Supervisor.

JSON Example
{
    "proxy_settings_source": "string",
    "https_proxy_config": "string",
    "http_proxy_config": "string",
    "no_proxy_config": [
        "string"
    ],
    "tls_root_ca_bundle": "string"
}
proxy_settings_source
Required

The settings can be inherited from the vCenter settings, so the cluster settings will be synced. The settings can be applied directly on the cluster level, or the cluster can be configured not to use a proxy.
VC_INHERITED : Proxy settings will be inherited from the vCenter settings. vCenter and cluster settings will be kept in sync.
CLUSTER_CONFIGURED : Proxy settings will be configured at the cluster level.
NONE : No proxy settings will be applied to the cluster.

string
https_proxy_config
Optional

HTTPS proxy configuration. Examples:

string
http_proxy_config
Optional

HTTP proxy configuration. Examples:

array of string
no_proxy_config
Optional

List of addresses that should be accessed directly. This will be used if CLUSTER_CONFIGURED is used for the source, otherwise this will be ignored. If unset there won't be any excluded addresses.

string
tls_root_ca_bundle
Optional

Proxy TLS root CA bundle which will be used to verify the proxy's certificates. Every certificate in the bundle is expected to be in PEM format. This will be used if CLUSTER_CONFIGURED is used for the source, otherwise this will be ignored. If unset only the vCenter certificates applied in VECS (VMware Endpoint Certificate Store) will be used.