In enterprise environments, it is a common practice to use HTTP(S) network proxies for connections to external networks and especially the internet. This comes at an additional configuration cost of all components that are running behind a proxy—we are going to give a brief overview of what components in Kubernetes you need to make the proxy aware to use Docker images from external registries and propagate the proxy settings to the containers.
Let's assume that our proxy addresses are as follows:
- http://proxy.example.com:8080/ for HTTP proxy
- http://proxy.example.com:9090/ for HTTPS proxy
Configuration for other standard proxies, such as SFTP, can be done similarly. You may also need appropriate no-proxy variables to exclude the Kubernetes nodes and local network, otherwise, you will be not able to communicate...
