Release Note

Last verified 1 Sep 2026

DigitalOcean Kubernetes (DOKS) now supports Isolated Worker Nodes in public preview. 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 enable isolation when you create a cluster running Kubernetes 1.36 or later.

We can't find any results for your search.

Try using different keywords or simplifying your search terms.