Configure the Bootstrap Cluster HTTP Proxy Settings

When creating a bootstrap cluster, you must locate the device used to create the bootstrap in the same proxied environment in which the workload cluster will run. D2iQ does not recommend creating a bootstrap cluster from outside a proxied environment.

When you first install DKP, the API server doesn’t exist yet in the bootstrap environment, because the API server is created during cluster creation. To create a bootstrap server in a proxied environment, you need to include the following flags:

• --http-proxy <<http proxy list>>

• --https-proxy <<https proxy list>>

• --no-proxy <<no proxy list>>

The following is an example dkp create bootstrap command’s syntax with the HTTP proxy settings included:

dkp create bootstrap --http-proxy <<http proxy list>> --https-proxy <<https proxy list>> --no-proxy <<no proxy list>>

Create a Bootstrap Cluster with HTTP Proxy Settings

Note that the delimiter between each proxy value within a flag is a comma ( , ) with no space character following it. The flags can include a mix of IP addresses and domain names.

1. If an HTTP proxy is required, locate the values to use for the http_proxy, https_proxy, and no_proxy flags. They will be built into the bootstrap cluster during cluster creation.

2. Create a bootstrap cluster using this command syntax, in addition to any other flags you may need:

   CODE

   dkp create bootstrap --kubeconfig $HOME/.kube/config \
     --http-proxy <string> \
     --https-proxy <string> \
     --no-proxy <string>

   This code sample shows the command with example values for the proxy settings:

   CODE

   dkp create bootstrap \
      --http-proxy 10.0.0.15:3128 \
      --https-proxy  10.0.0.15:3128 \
      --no-proxy 127.0.0.1,192.168.0.0/16,10.0.0.0/16,10.96.0.0/12,169.254.169.254,169.254.0.0/24,localhost,kubernetes,kubernetes.default,kubernetes.default.svc,kubernetes.default.svc.cluster,kubernetes.default.svc.cluster.local,.svc,.svc.cluster,.svc.cluster.local,.svc.cluster.local.,kubecost-prometheus-server.kommander,logging-operator-logging-fluentd.kommander.svc.cluster.local,elb.amazonaws.com

Next Step

Create CAPI Components with HTTP/HTTPS Proxy Settings