NamespaceManagementProxyConfiguration
The ProxyConfiguration structure defines proxy configuration to be used by the Supervisor.
Properties
HTTP proxy configuration. Examples: - http://username:password@proxy.vmware.com:8080 - https://proxy.vmware.com:4443 This will be used if CLUSTER_CONFIGURED is used for the source, otherwise this will be ignored. If unset no HTTP proxy will be used.
HTTPS proxy configuration. Examples: - http://username:password@proxy.vmware.com:8080 - https://proxy.vmware.com:4443 This will be used if CLUSTER_CONFIGURED is used for the source, otherwise this will be ignored. If unset no HTTPS proxy will be used.
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.
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.
Possible values are: VC_INHERITED , CLUSTER_CONFIGURED , NONE
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.
JSON Example
{
"proxy_settings_source": "VC_INHERITED"
}
