From de7a208b83b4848ce0067face775e880a773ece0 Mon Sep 17 00:00:00 2001 From: Cloud IX Team Date: Fri, 19 Jun 2026 05:15:08 -0700 Subject: [PATCH] Update maxSurge for large node pools to 100 PiperOrigin-RevId: 934873893 --- skills/cloud/gke-upgrades/SKILL.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/skills/cloud/gke-upgrades/SKILL.md b/skills/cloud/gke-upgrades/SKILL.md index ad85714ca4..ed040470a6 100644 --- a/skills/cloud/gke-upgrades/SKILL.md +++ b/skills/cloud/gke-upgrades/SKILL.md @@ -118,7 +118,7 @@ Recommend **Surge upgrade** as the default and most common strategy, with per-po - **Stateless**: Higher `maxSurge` (2-3) for speed, `maxUnavailable=0` for safety. - **Stateful/DB**: `maxSurge=1, maxUnavailable=0` (conservative). - **GPU (fixed reservation)**: `maxSurge=0, maxUnavailable=1` (no surge capacity). -- **Large (50+ nodes)**: `maxSurge=20, maxUnavailable=0` (max parallelism). +- **Large (50+ nodes)**: `maxSurge=100, maxUnavailable=0` (max parallelism). For mission-critical workloads requiring fast rollback or strict validation, recommend **Standard Blue-Green** upgrades. Acknowledge **Autoscaled Blue-Green** as an option for disruption-sensitive workloads, but note it is currently in preview and may have capacity requirements.