Using HTTP/S Proxy with KIB Images

In some networked environments, the machines used for building images can reach the Internet, but only through an HTTP/S proxy. For DKP to operate in these networks, you need a way to specify what proxies to use.  You can use an HTTP proxy override file to specify that proxy. When KIB is trying to install a particular OS package, it uses that proxy to reach the Internet to download that package.

The proxy setting specified here is NOT “baked into” the image - it is only used while the image is being built. The settings are removed before the image is finalized.

While it might seem logical to include the proxy information in the image, the reality is that many companies have multiple proxies - one perhaps for each geographical region, or maybe even a proxy per Datacenter or office.  All network traffic to the Internet goes through the proxy. If you were in Germany, you would probably not want to send all your traffic to a U.S.-based proxy. Doing that would slow traffic down and consume too many network resources. If you baked the proxy settings into the image, you would have to create a separate image for each specific region. It makes more sense to create an image with no proxy included, but remember that you still need a proxy to access the Internet. Thus, when creating the cluster, (and also when installing the Kommander component of DKP), you must specify the correct proxy settings for the network environment into which you are installing the cluster. You will use the same base image for that cluster as one installed in an environment with different proxy settings.

See: HTTP Proxy Override Files

Related Topic

Pre-Provisioned Override Files

Next Topic

Private Registry in Air-gapped Override

Next Step

Either navigate to the main Konvoy Image Builder section of the documentation or back to your installation section:

• If using the Day 1- Basic Install instructions, proceed (or return) to that section Day 1 - Basic Installs by Infrastructure combinations to install and setup DKP based on your infrastructure environment provider.

• If using the Custom Install instructions, proceed (or return) to that section and select the infrastructure provider you are using: Custom Installation and Additional Infrastructure Tools