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, integrate natively with DigitalOcean Load Balancers and volumes, and can be managed programmatically using the API and command line. For critical workloads, add the high-availability control plane to increase uptime with 99.95% SLA.
To create a Kubernetes cluster:
Once the cluster is created, use
kubectl to manage it.
To get started with DigitalOcean Kubernetes, see our Build and Deploy Your First Image to Your First Cluster tutorial.
You can add a variety of preconfigured apps and stacks to a new or existing Kubernetes cluster.
Alternatively, locate the app you want to install in the DigitalOcean Marketplace and click Install App on the upper right. Select whether to install the app on a new or existing cluster.
For more details about the 1-Click apps, see Manage 1-Click Applications.
The Kubernetes Dashboard provides a web-based user interface where you can deploy containerized applications, troubleshoot your application, manage your cluster resources (such as Deployments, Jobs, DaemonSets, etc), get an overview of applications running on your cluster, initiate a rolling update, restart a pod, and more.
For more details on how to use the Kubernetes Dashboard, see Web UI (Dashboard) in the Kubernetes documentation.
You can create additional node pools and add and remove nodes from a node pool at any time.
To edit the size of an existing node pool:
To add additional node pools:
If a worker node isn’t functioning properly, you can destroy and replace it with a new node of the same type with the Recycle option.
Open the cluster’s … menu and select View Nodes.
Click the name of the node pool with the problem node.
Open the … menu next to the problem node and select Recycle.
Optionally, if you want to skip draining the node before removing it, uncheck the Drain node when replacing checkbox.
By default, the workloads are drained from the node before the node is removed. Skipping node draining is useful when you know that a drain will fail because the workload is broken or cannot gracefully terminate.
Click Recycle to confirm the action.
Recycling a worker node replaces the underlying Droplet with a newly provisioned one. Attached volumes will be detached and reattached to the new Droplet, but any data stored locally on the original Droplet’s disk will be lost.
To delete an entire cluster:
Destroying a cluster does not delete DigitalOcean Load Balancers or volumes associated with the cluster.