API v2 Changelog

< Back to Changelog

Persistent Node Pool Taints for DigitalOcean Kubernetes

Date: October 6, 2020

Tagged In: API v2

Author Dan Brian

You can now apply taints to Kubernetes node pools. When you configure taints for a node pool, the taint automatically applies to all current nodes in the pool and any node you add to the pool thereafter. For more information about taints and tolerations, see Kubernetes’ documentation.

Additionally, we’ve added node taint support for our official clients, godo and doctl. Only versions of doctl 1.47.0 and godo 1.45.0 and above support persistent node pool taints.

You can define taints during a pool’s creation by submitting a POST request to the /v2/kubernetes/clusters/<cluster-id>/node_pools and the /v2/kubernetes/clusters endpoints, or you can update existing pools by submitting a PUT request to the /v2/kubernetes/clusters/<cluster-id>/node_pools/<node-pool-id> endpoint. For example, this request body defines two taints for a node pool.

  "name": "frontend",
  "size": 10,
  "taints": [
      "key": "priority",
      "value": "high",
      "effect": "NoSchedule",
      "key": "workloadKind",
      "value": "database",
      "effect": "NoExecute",