How to Create Kubernetes Clusters Using the Control Panel

DigitalOcean Kubernetes (DOKS) is a managed Kubernetes service that lets you deploy Kubernetes clusters without the complexities of handling the control plane and containerized infrastructure. Clusters are compatible with standard Kubernetes toolchains and integrate natively with DigitalOcean Load Balancers and block storage volumes.

You can create a DigitalOcean Kubernetes Cluster at any time from the DigitalOcean Control Panel by opening the Create menu in the top right.

The create menu

In the Create menu, click Kubernetes to go to the Create a cluster page. On this page, you’ll choose a Kubernetes version, datacenter region, and cluster capacity for your cluster and then create it.

Select a Kubernetes version

The latest patch version for the three most recent minor versions of Kubernetes are available for new cluster creation. The latest stable release is selected by default.

Choose a datacenter region

Choose the region for your cluster. Your cluster’s control plane and worker nodes will be located in the same region.

If you plan to use block storage volumes for persistent data storage, choose a region with block storage support. If you add a DigitalOcean Load Balancer to your deployment, it will automatically be placed in the same region as the cluster.

VPC Network

In the VPC Network section, choose a VPC network for the cluster. You can choose one you’ve created or use your default network for the datacenter region. VPC enables an additional networking interface that can only be accessed by other resources within the same VPC network. This keeps traffic between Droplets and other applicable resource from being routed outside the datacenter over the public internet.

Choose cluster capacity

To create a cluster, you need to add at least one node pool with at least one worker. Specify the following fields for the node pool:

  • Node pool name. Choose a name for the node pool when it’s created. Nodes inside this pool inherit this naming scheme when they are created. If you rename the node pool later, the nodes will only inherit the new naming scheme when they are recreated (when you recycle the nodes or resize the node pool).

  • Machine type (Droplet). Choose if you want your worker nodes to be backed by Basic (Standard CPU, Premium Intel CPU, or Premium AMD CPU), General Purpose, or CPU-Optimized Droplet plans.

  • Node plan. Choose the specific plan you want for your worker nodes. Each of the workers in a node pool has identical resources.

    To take advantage of different resource capacities, you can add additional node pools with the Add Additional Node Pool button and assign pods to the node pools with the appropriate scheduling constraints.

  • Number nodes. Choose how many nodes to include in the node pool. By default, three worker nodes are selected because this is the minimum number to ensure high availability.

One-node clusters are an inexpensive option to begin learning Kubernetes or for a development environment where resiliency isn’t a concern. However, a stand-alone Droplet with a container runtime or minikube will generally give you better performance than a one-node cluster for the same cost.

At the bottom of this section, you’ll see the monthly rate for your cluster based on the resources you’ve chosen. When you create the cluster, billing begins for each resource (e.g. worker nodes, block storage volumes, load balancers) as it is created and ends as it is destroyed.

Optionally, you can choose the high-availability option (in Early Availability) during cluster creation.


Finalize the cluster settings. You can specify a name, assign a project, and optionally add tags to the cluster.


By default, cluster names begin with k8s, followed by the version of Kubernetes, the datacenter region, and the cluster ID. You can customize the cluster name, which will also be used in the tag.


The new cluster belongs to your default project. You can assign the cluster to a different project.

You can also change the project after you create the cluster. Go to the Kubernetes page in the control panel. From the cluster’s More menu, select Move to and select the project you want to move the cluster to.

Associated resources, such as load balancers and block storage volumes, also move when you move the cluster to a different project.

Due to a known issue, resources associated with a cluster are added to the default project upon creation. The resources will move to the cluster’s project after you resize or move the cluster between projects.


Clusters automatically have three tags:

  • k8s
  • The specific cluster ID, like k8s:EXAMPLEc-3515-4a0c-91a3-2452eEXAMPLE
  • The resource type, e.g. k8s:worker

You can also add custom tags to a cluster and its node pools in the cluster’s Overview and Nodes pages. Any custom tags you add to worker nodes in a node pool (for example, from the Droplets page), are deleted to maintain consistency between the node pool and its worker nodes.

Create Cluster

When you have entered your settings, create the cluster by clicking the Create Cluster button. It can take several minutes for cluster creation to finish.

Once your cluster is provisioned, you can view cluster information such as the cluster capacity, cost, and cluster ID in the Overview tab.

Overview tab

To manage the cluster, use kubectl, the official Kubernetes command-line client. See How to Connect to a DigitalOcean Kubernetes Cluster to get set up.