Pattern: Disabled surge upgrades for Kubernetes cluster
Issue: -
While upgrading your cluster, workloads will temporarily be moved to new nodes. A small cost will follow, but as a bonus, you won't experience downtime.
Resolution: Enable surge upgrades in your Kubernetes cluster.
The following example will fail the digitalocean-compute-surge-upgrades-not-enabled check.
resource "digitalocean_kubernetes_cluster" "surge_upgrade_bad" {
name = "foo"
region = "nyc1"
version = "1.20.2-do.0"
surge_upgrade = false
node_pool {
name = "worker-pool"
size = "s-2vcpu-2gb"
node_count = 3
taint {
key = "workloadKind"
value = "database"
effect = "NoSchedule"
}
}
}The following example will pass the digitalocean-compute-surge-upgrades-not-enabled check.
resource "digitalocean_kubernetes_cluster" "surge_upgrade_good" {
name = "foo"
region = "nyc1"
version = "1.20.2-do.0"
surge_upgrade = true
node_pool {
name = "worker-pool"
size = "s-2vcpu-2gb"
node_count = 3
taint {
key = "workloadKind"
value = "database"
effect = "NoSchedule"
}
}
}