oxofrmbl/jitsi-meet
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

ci: rollout-restart deployments after apply (ConfigMap drift propagation)
All checks were successful
deploy / deploy (push) Successful in 21s
Details

Browse Source
This commit is contained in:
Dennis Paradzinski 2026-05-11 15:36:09 +02:00
parent 8e76a96668
commit 3358272cf7
1 changed files with 7 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

7
.gitea/workflows/deploy.yml
View File

@ -46,6 +46,13 @@ jobs:
kubectl apply -f infra/k3s/60-jvb.yaml kubectl apply -f infra/k3s/60-jvb.yaml
kubectl apply -f infra/k3s/70-ingress.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 - name: Wait for rollout
run: | run: |
kubectl -n jitsi rollout status deployment/prosody --timeout=3m kubectl -n jitsi rollout status deployment/prosody --timeout=3m