This topic describes how HTTP/HTTPS proxies work in Tanzu Kubernetes Grid Integrated Edition (TKGI) on AWS, and how to set proxies globally.
To configure proxy settings specifically for individual TKGI clusters, see Configure Cluster Proxies.
If your environment includes HTTP proxies, you can configure Tanzu Kubernetes Grid Integrated Edition on AWS to use these proxies so that Tanzu Kubernetes Grid Integrated Edition-deployed Kubernetes control plane and worker nodes access public Internet services and other internal services through a proxy.
In addition, Tanzu Kubernetes Grid Integrated Edition proxy settings apply to the TKGI API instance. When an Tanzu Kubernetes Grid Integrated Edition operator creates a Kubernetes cluster, the TKGI API VM behind a proxy is able to manage AWS components on the standard network.
You can also proxy outgoing HTTP/HTTPS traffic from Ops Manager and the BOSH Director so that all Tanzu Kubernetes Grid Integrated Edition components use the same proxy service.
The following diagram illustrates the network architecture:
To configure a global HTTP proxy for all outgoing HTTP/HTTPS traffic from the Kubernetes cluster nodes and the TKGI API server, perform the following steps:
Navigate to Ops Manager and log in.
Click the Tanzu Kubernetes Grid Integrated Edition tile.
Note: This setting does not set the proxy for running Kubernetes workloads or pods.
To complete your global proxy configuration for all outgoing HTTP/HTTPS traffic from your Kubernetes clusters, perform the following steps:
Note: Using an HTTPS connection to the proxy server is not supported. HTTP and HTTPS proxy options can only be configured with an HTTP connection to the proxy server. You cannot populate either of the proxy URL fields with an HTTPS URL. The proxy host and port can be different for HTTP and HTTPS traffic, but the proxy protocol must be HTTP.
127.0.0.1,localhost, *.example1.com, .example2.com, example3.com, 198.51.100.0/24, 203.0.113.0/24, 192.0.2.0/24
Note: By default the
10.200.0.0/8 IP address ranges,
.svc.cluster, and your Tanzu Kubernetes Grid Integrated Edition FQDN are not proxied. This allows internal Tanzu Kubernetes Grid Integrated Edition communication.
Do not use the
_ character in the No Proxy field. Entering an underscore character in this field can cause upgrades to fail.
Because some jobs in the VMs accept
\*. as a wildcard, while others only accept
., we recommend that you define a wildcard domain using both of them. For example, to denote
example.com as a wildcard domain, add both
example.com to the No Proxy property.
To save your changes to the TKGI tile, click Save.
To enable an HTTP proxy for outgoing HTTP/HTTPS traffic from Ops Manager and the BOSH Director, perform the following steps:
Log in to Ops Manager.
Select User Name > Settings in the upper right.
Click Proxy Settings.
Under HTTP Proxy, enter the FQDN or IP address of the HTTP proxy endpoint. For example,
Under HTTPS Proxy, enter the FQDN or IP address of the HTTPS proxy endpoint. For example,
Note: Using an HTTPS connection to the proxy server is not supported. Ops Manager and BOSH HTTP and HTTPS proxy options can be only configured with an HTTP connection to the proxy.
Under No Proxy, include the hosts that must bypass the proxy. This is required.
In addition to
localhost, include the BOSH Director IP, Ops Manager IP, TKGI API VM IP, and the TKGI Database VM IP. If the TKGI Database is in HA mode (beta), enter all your database IPs in the No Proxy field.
Note: Ops Manager does not allow the use of a CIDR range in the No Proxy field. You must specify each individual IP address to bypass the proxy.
The No Proxy field does not accept wildcard domain notation, such as
.docker.com. You must specify the exact IP or FQDN to bypass the proxy, such as
Return to the Ops Manager Installation Dashboard and click Review Pending Changes.
Click Apply Changes to deploy Ops Manager and the BOSH Director with the updated proxy settings.