sorb/axion1337.chat-gitops
1
0
Fork 0
Code Issues Pull Requests Packages Projects 1 Releases 24 Wiki Activity

docs(coturn): note the one-time manual rollingUpdate fix instead of an ineffective YAML null
Auto-Deploy on Push / verify-and-notify (push) Canceled after 0s

Browse Source
This commit is contained in:
Thore Cimbal
2026-07-28 21:10:28 +02:00
parent d24dbf84f7
commit e53896e02c
1 changed files with 6 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files
apps/production/coturn.yaml
+6 -1
View File
@@ -68,9 +68,14 @@ spec:
# hostNetwork pods bind directly to the node's ports (3478/5349) - on this single-node # hostNetwork pods bind directly to the node's ports (3478/5349) - on this single-node
# cluster, RollingUpdate's default "bring up the new pod before removing the old one" # cluster, RollingUpdate's default "bring up the new pod before removing the old one"
# can never schedule (port conflict). Recreate kills the old pod first. # can never schedule (port conflict). Recreate kills the old pod first.
# Note: switching to Recreate on an existing Deployment that already had the
# RollingUpdate defaults recorded required a one-time manual
# `kubectl patch --type=merge -p '{"spec":{"strategy":{"rollingUpdate":null,"type":"Recreate"}}}'`
# (2026-07-28) - a YAML `rollingUpdate: null` in this file is dropped before reaching the
# API server (client-side omits null keys) rather than sent as an explicit field deletion,
# so it can't clear an already-set field on its own.
strategy: strategy:
type: Recreate type: Recreate
rollingUpdate: null
selector: selector:
matchLabels: matchLabels:
app: coturn app: coturn