ci: rollout-restart deployments after apply (ConfigMap drift propagation)

.gitea/workflows/deploy.yml

@@ -46,6 +46,13 @@ jobs:
           kubectl apply -f infra/k3s/60-jvb.yaml
           kubectl apply -f infra/k3s/70-ingress.yaml
 
+      # ConfigMap-only changes don't restart pods on their own, so a
+      # deploy that just edits 10-config.yaml would otherwise leave the
+      # pods running the old env vars. Force a rollout to pick the new
+      # values up — no-op when no spec drift, fast when there is.
+      - name: Roll pods to pick up ConfigMap drift
+        run: kubectl -n jitsi rollout restart deployment
+
       - name: Wait for rollout
         run: |
           kubectl -n jitsi rollout status deployment/prosody --timeout=3m