Spot-Only GKE Capacity Without Standard Fallback

Go back

Hierony Manurung

CER:

GCP-Compute-7619

Service Category

Compute

Cloud Provider

GCP

Service Name

GCP GKE

Inefficiency Type

Availability-driven waste

Explanation

This inefficiency occurs when workloads are constrained to run only on Spot-based capacity with no viable path to standard nodes when Spot capacity is reclaimed or unavailable. While Spot reduces unit cost, rigid dependence can create hidden costs by requiring standby standard capacity elsewhere, delaying deployments, or increasing operational intervention to keep environments usable. GKE explicitly recommends mixing Spot and standard node pools for continuity when Spot is unavailable.

Relevant Billing Model

Spot VMs are discounted but have no availability guarantees; relying on Spot-only capacity can force compensating spend (extra standard capacity, retries, and operational overhead) to maintain reliability.

Detection

Review whether critical or time-sensitive workloads rely exclusively on Spot-based capacity
Assess whether the environment can continue operating acceptably during Spot interruptions
Identify patterns where teams maintain separate standard capacity “just in case” due to Spot uncertainty

Remediation

Treat Spot as preferred (where appropriate), not exclusive, capacity
Maintain sufficient standard capacity to keep essential workloads running when Spot capacity is reclaimed or temporarily unavailable

Relevant Documentation

Submit Feedback