For AI agents: The documentation index is at https://docs.digitalocean.com/llms.txt. Markdown versions of pages use the same URL with index.html.md in place of the HTML page (for example, append index.html.md to the directory path instead of opening the HTML document).

Getting Started

Quickstarts and intermediate tutorials to get started.

How-Tos

How to accomplish specific tasks in detail, like creation/deletion, configuration, and management.

Reference

API and CLI reference documentation for the DigitalOcean Kubernetes service, including example requests and available parameters.

Concepts

Explanations and definitions of core concepts in Kubernetes.

Details

Features, plans and pricing, availability, limits, known issues, and more.

Support

Get help with technical support and answers to frequently asked questions.

Related Links

Is Kubernetes Right for Me?

Choosing the best deployment platform for your business.

High-Availability Control Plane for DOKS Clusters

Maximize reliability for critical workloads and environments.

Kubernetes Bootstrapper

Framework to set up production-grade clusters.

Kubernetes Adoption Journey

Hands-on tutorial for going from day one to production on DOKS.

Case Studies

How customers build and scale their applications using DOKS and other DigitalOcean services.

Marketplace

Learn Kubernetes by starting with one of our preconfigured stacks.

Changelog

DigitalOcean Kubernetes Changelog

Notable changes for each available version of DigitalOcean Kubernetes and archives of changes for unavailable versions.

Latest Updates

8 October 2026

• Starting with DOKS 1.37, GPU device plugins are no longer enabled by default on clusters with GPU nodes. Dynamic Resource Allocation (DRA) drivers are available as opt-in cluster plugins (nvidia_gpu_dra_driver or amd_gpu_dra_driver). Device plugins (nvidia_gpu_device_plugin or amd_gpu_device_plugin) remain available but must be enabled explicitly. Device plugins and DRA drivers are mutually exclusive. When you switch between them on an existing cluster, DOKS replaces the GPU worker nodes so each node starts with a clean state. For more information, see Supported GPUs.

• When you upgrade an existing DigitalOcean Kubernetes (DOKS) cluster to version 1.37 or later, DOKS automatically enables the CoreDNS Cluster Proportional Autoscaler (CPA) plugin if CoreDNS is still running the default of two replicas. If you have manually changed the CoreDNS replica count, DOKS leaves it as is, and you can enable CPA yourself. CPA is already enabled by default on new clusters running Kubernetes 1.36 or later. For more information, see How to Configure CoreDNS Autoscaling.

29 September 2026

• Isolated Worker Nodes for DigitalOcean Kubernetes (DOKS) are now in general availability. Every worker node in an isolated cluster runs without a public IPv4 address, so nodes are removed from the public internet at the network level rather than only protected by a firewall.

  Outbound traffic, including node provisioning and container image pulls, routes through a VPC NAT Gateway, and other resources in the same VPC reach the nodes over private addresses. The Kubernetes API server stays publicly reachable so you can still manage the cluster. You can enable isolation only when you create a cluster running Kubernetes 1.36 or later.

10 September 2026

• The DigitalOcean Control Panel now supports adding and removing allow and deny rules based on IP addresses and CIDR ranges when you create or manage regional load balancers that use HTTP or Network traffic management. See How to Create Regional Load Balancers and How to Manage Regional Load Balancers. Global load balancers do not support firewall rules, and DigitalOcean Kubernetes (DOKS)-managed load balancers continue to use Kubernetes service configuration.

For more information, see all Kubernetes release notes.