DigitalOcean Logo

DigitalOcean Kubernetes Billing Updates

Changes to billing for DigitalOcean Kubernetes starting July 1, 2022

To simplify billing across DigitalOcean Kubernetes, and to better serve our broad range of customers, we’re making changes to DigitalOcean Kubernetes billing, including a 672-hour monthly cap on node pool billing and a switch to simpler per-second billing. 

Here are more details about the DigitalOcean Kubernetes billing changes:

Billing at a node-pool level


A DigitalOcean Kubernetes cluster typically has one or more node pools. Each node pool consists of a group of identical worker nodes. Users are currently billed for DigitalOcean Kubernetes at a worker node level, but will be billed at a node pool level instead starting July 1, 2022. Your bill will now depend on the configuration and usage of your node pools in that month. 

Per-second billing 

We currently round up or down your DigitalOcean Kubernetes bill to the nearest hour. However, this level of granularity isn’t sufficient for DigitalOcean Kubernetes since it’s quite common for worker nodes to autoscale multiple times in an hour. To simplify and improve the accuracy of your DigitalOcean Kubernetes bill, we’re switching to per-second billing for node pools. 

A monthly cap of 672 hours for predictable bills

Billing for node pools will have a monthly cap of 672 hours (28 days multiplied by 24 hours), so node pools that are active for more than 672 hours in a month will only be billed at 672 hours. This cap makes your monthly bill more predictable and ensures that it doesn’t change based on the varying number of hours in a given month. For example, the bill for a node pool in January (a month with 744 hours) will now be the same as the bill in February (a month with 672 hours). Note that DigitalOcean resources are priced per-month, and the new pricing model for DigitalOcean Kubernetes is similar to how Droplet pricing works. 

The billing clock starts when a node in the node pool first becomes ready 

You won’t be billed for the time taken for a node instantiation. Also you will not be charged for nodes that were created but that never joined the cluster. You will still be billed for all nodes that are part of your cluster, even if they’re unhealthy.

Access surge upgrades for free

Surge upgrades will be available at no charge, ensuring a faster and more stable upgrade when you need it most. They create duplicate nodes, up to a maximum of 10 nodes. After the upgraded nodes are created, workloads are drained from the old nodes to the new nodes before deleting the old nodes. You will not be charged for the extra nodes created during surge upgrades.

Please click here for more details.