From a9cb218d597099bd78bff0ee848061e28f5191e0 Mon Sep 17 00:00:00 2001
From: E M <5089238+emizzle@users.noreply.github.com>
Date: Fri, 1 May 2026 11:36:53 +1000
Subject: [PATCH] Keep 1 node alive so autoscaler doesn't scale to 0

Should help speed up startup, avoiding errors like "pod couldn't be scheduled"
---
 .github/release/clusters/modules/gke/main.tf | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/.github/release/clusters/modules/gke/main.tf b/.github/release/clusters/modules/gke/main.tf
index 20ba678e..8bc4928a 100644
--- a/.github/release/clusters/modules/gke/main.tf
+++ b/.github/release/clusters/modules/gke/main.tf
@@ -38,11 +38,11 @@ resource "google_container_cluster" "this" {
 
   node_pool {
     name               = var.tests_pool_name
-    initial_node_count = 0
+    initial_node_count = 1
     node_locations     = length(var.tests_pool_zones) > 0 ? var.tests_pool_zones : null
 
     autoscaling {
-      min_node_count = 0
+      min_node_count = 1
       max_node_count = var.tests_pool_max
     }