Skip to main content
Skip table of contents

DKP Enterprise Quick Start

This page provides generic instructions for getting started with DKP, to get your Kubernetes cluster up and running with basic configuration requirements. Each Infrastructure Provider will have different steps. If your provider is listed in the Table of Contents with a Quick Start, please begin there instead. For AKS and EKS, please follow the steps below first before beginning a Quick Start for either AKS or EKS.

If your provider or environment is different than AKS or EKS, please see that provider's Quick Start page instead.


Before starting the DKP installation, verify that you have:

  • An x86_64-based Linux or macOS machine with a supported version of the operating system.

  • The dkp binary for Linux, or macOS.

  • Docker version 18.09.2 or later.

  • kubectl for interacting with the running cluster.

  • A valid infrastructure provider account with credentials configured.

  • Resource requirements

If your environment uses HTTP/HTTPS proxies, you must include the flags --http-proxy, --https-proxy, and --no-proxy and their related values in commands for creating clusters or CAPI objects for the command to be successful. More information is available in Configure HTTP Proxy.

Create a new Kubernetes cluster

Create/deploy a cluster using the command below:

kubectl create -f ${DKP_CLUSTER_NAME}.yaml

If you wish to watch the cluster build, run the command below:

dkp describe cluster -c ${DKP_CLUSTER_NAME}

Pivot the Cluster Controllers and Create CAPI Controllers on Cluster with this command:

./dkp create capi-components --kubeconfig ${DKP_CLUSTER_NAME}.conf

Once created, move the configuration to the new cluster using the command below:

./dkp move --to-kubeconfig ${DKP_CLUSTER_NAME}.conf

You now have a Self-Managing Kubernetes Cluster deployed. Proceed to the Quick Start Guide of the Infrastructure Provider of your choice below:

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.