Configuring an HTTP/HTTPS Proxy

When creating a DKP cluster in environments that use an HTTP/HTTPS proxy, you must provide proxy details. The proxy values are strings that list a set of proxy servers, URLs, or wildcard addresses that is specific to your environment.

When creating a DKP cluster in a proxied environment, you need to specify proxy settings for the:

• Bootstrap cluster

• CAPI components

• DKP Kommander component

When you create a DKP cluster using the --self-managed flag, the bootstrap cluster and CAPI components are created for you automatically, and use the HTTP and HTTPS proxy settings you specify in the dkp create cluster <provider>... command.

You can also create the bootstrap cluster and CAPI components manually, using the appropriate commands, dkp create bootstrap and dkp create capi-components respectively, combined with the command line flags to include your HTTP/S proxy information.

You can also specify HTTP/S proxy information in an override file when using Konvoy Image Builder (KIB).

Without these values provided as part of the relevant dkp create command, DKP cannot create the requisite parts of your new cluster correctly. This is true of both management and managed clusters alike.

For DKP installation, you should create the bootstrap cluster from within the same network in which the new cluster will run. Using a bootstrap cluster on a laptop with different proxy settings, for example, or residing in a different network, could cause problems.

Next Steps for HTTP/HTTPS Proxy

You can define HTTP/HTTPS proxy information using the steps in these pages:

Related Topic

HTTP Status Codes

Next Topics

If HTTP does not apply, proceed to any of the next topics:

• Working with Load Balancers

• Customizing CAPI Components for a Cluster

• Registry and Registry Mirrors

• Subnets and Pods