Proxy

Proxy support (optional)

Provider support details

You can configure EKS Anywhere to use a proxy to connect to the Internet. This is the generic template with proxy configuration for your reference:

apiVersion: anywhere.eks.amazonaws.com/v1alpha1 kind: Cluster metadata:  name: my-cluster-name spec:  ...  proxyConfiguration:  httpProxy: http-proxy-ip:port  httpsProxy: https-proxy-ip:port  noProxy:  - list of no proxy endpoints 

Configuring Docker daemon

EKS Anywhere will proxy for you given the above configuration file. However, to successfully use EKS Anywhere you will also need to ensure your Docker daemon is configured to use the proxy.

This generally means updating your daemon to launch with the HTTPS_PROXY, HTTP_PROXY, and NO_PROXY environment variables.

For an example of how to do this with systemd, please see Docker’s documentation here .

Configuring EKS Anywhere proxy without config file

For commands using a cluster config file, EKS Anywhere will derive its proxy config from the cluster configuration file.

However, for commands that do not utilize a cluster config file, you can set the following environment variables:

export HTTPS_PROXY=https-proxy-ip:port export HTTP_PROXY=http-proxy-ip:port export NO_PROXY=no-proxy-domain.com,another-domain.com,localhost 

Proxy Configuration Spec Details

proxyConfiguration (required)

• Description: top level key; required to use proxy.
• Type: object

httpProxy (required)

• Description: HTTP proxy to use to connect to the internet; must be in the format IP:port
• Type: string
• Example: httpProxy: 192.168.0.1:3218

httpsProxy (required)

• Description: HTTPS proxy to use to connect to the internet; must be in the format IP:port
• Type: string
• Example: httpsProxy: 192.168.0.1:3218

noProxy (optional)

• Description: list of endpoints that should not be routed through the proxy; can be an IP, CIDR block, or a domain name
• Type: list of strings
• Example

 noProxy:  - localhost  - 192.168.0.1  - 192.168.0.0/16  - .example.com