From 5e1e18a0449b0f475b84c112c900bc562400f881 Mon Sep 17 00:00:00 2001
From: Viktor Barzin <viktorbarzin@meta.com>
Date: Tue, 10 Feb 2026 21:28:38 +0000
Subject: [PATCH] [ci skip] Use RollingUpdate strategy for real-estate-crawler
 deployments

Set max_unavailable=0, max_surge=1 on both UI and API deployments
to ensure at least 1 replica is always available during updates.
---
 modules/kubernetes/real-estate-crawler/main.tf | 16 ++++++++++++----
 1 file changed, 12 insertions(+), 4 deletions(-)

diff --git a/modules/kubernetes/real-estate-crawler/main.tf b/modules/kubernetes/real-estate-crawler/main.tf
index bd885402..2758fbae 100644
--- a/modules/kubernetes/real-estate-crawler/main.tf
+++ b/modules/kubernetes/real-estate-crawler/main.tf
@@ -33,9 +33,13 @@ resource "kubernetes_deployment" "realestate-crawler-ui" {
   }
   spec {
     replicas = 1
-    # strategy {
-    #   type = "RollingUpdate" # DB is external so we can roll
-    # }
+    strategy {
+      type = "RollingUpdate"
+      rolling_update {
+        max_unavailable = 0
+        max_surge       = 1
+      }
+    }
     selector {
       match_labels = {
         app = "realestate-crawler-ui"
@@ -102,7 +106,11 @@ resource "kubernetes_deployment" "realestate-crawler-api" {
   spec {
     replicas = 1
     strategy {
-      type = "Recreate"
+      type = "RollingUpdate"
+      rolling_update {
+        max_unavailable = 0
+        max_surge       = 1
+      }
     }
     selector {
       match_labels = {