From eca2ee56c009ffa69ace7b0fae4f4a4fdfa443ac Mon Sep 17 00:00:00 2001 From: Your Name Date: Mon, 21 Sep 2026 19:40:26 +0800 Subject: [PATCH] fix(deploy): update rollout commands for StatefulSet migration im-server moved from Deployment to StatefulSet in im-deploy-config (native Cluster enablement) -- this workflow's kubectl commands still targeted the old resource type, so every deploy since the migration failed at the final step with "deployments.apps im-server not found" (image built/pushed fine, just never got rolled out). Co-Authored-By: Claude Sonnet 5 --- .gitea/workflows/deploy.yml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/.gitea/workflows/deploy.yml b/.gitea/workflows/deploy.yml index eb16958..2680269 100644 --- a/.gitea/workflows/deploy.yml +++ b/.gitea/workflows/deploy.yml @@ -34,5 +34,5 @@ jobs: mkdir -p ~/.kube echo "${{ secrets.KUBECONFIG }}" > ~/.kube/config chmod 600 ~/.kube/config - kubectl rollout restart deployment/im-server -n im-server-system - kubectl rollout status deployment/im-server -n im-server-system --timeout=120s + kubectl rollout restart statefulset/im-server -n im-server-system + kubectl rollout status statefulset/im-server -n im-server-system --timeout=120s