From d24dbf84f72c48c3a24a72c9df282708fb56c34c Mon Sep 17 00:00:00 2001 From: Thore Cimbal Date: Tue, 28 Jul 2026 21:08:22 +0200 Subject: [PATCH] fix(coturn): explicitly null rollingUpdate field alongside Recreate strategy Server-side apply left the old RollingUpdate defaults (maxSurge/maxUnavailable) on the live object from before strategy.type was ever set explicitly, which the API rejects when combined with type: Recreate. Explicit null clears it. Co-Authored-By: Claude Sonnet 5 --- apps/production/coturn.yaml | 1 + 1 file changed, 1 insertion(+) diff --git a/apps/production/coturn.yaml b/apps/production/coturn.yaml index e236b08..ddac3f1 100644 --- a/apps/production/coturn.yaml +++ b/apps/production/coturn.yaml @@ -70,6 +70,7 @@ spec: # can never schedule (port conflict). Recreate kills the old pod first. strategy: type: Recreate + rollingUpdate: null selector: matchLabels: app: coturn