Creating CAPI components for a DKP cluster from the command line requires HTTP/HTTPS proxy information, if your environment is proxied.
If you created a cluster without using the
--self-managed flag, the cluster will not have any of the CAPI controllers or the cert-manager component. This means that the cluster will be managed from the context of the cluster from which it was created such as the bootstrap cluster. However, you can transform the cluster to a self-managed cluster by performing the commands:
dkp create capi-components --kubeconfig=<newcluster>
dkp move --to-kubeconfig=<newcluster>
This combination of actions is sometimes called a pivot.
When creating the CAPI components for a proxied environment using the DKP command line interface, you must 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 capi-components command’s syntax with the HTTP proxy settings included:
dkp create capi-components --http-proxy <<http proxy list>> --https-proxy <<https proxy list>> --no-proxy <<no proxy list>>
Create CAPI Components 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.
If an HTTP proxy is required, locate the values to use for the
no_proxyflags. They will be built into the CAPI components during their creation.
Create CAPI components using this command syntax, in addition to any other flags you may need:CODE
dkp create capi-components --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 capi-components \ --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