From 7c866575485e255dcfec2fe24228c91bc3d06bfd Mon Sep 17 00:00:00 2001 From: claude Date: Sun, 31 May 2026 21:30:45 +0000 Subject: [PATCH] CI: pull deploy image via public registry address The cluster nodes' containerd can only pull from registry.alocoq.fr, not the in-cluster service name. Keep pushing via the in-cluster address (to bypass the Traefik upload-timeout), but reference registry.alocoq.fr/verso in the test Deployment and the rolling update. Both addresses front the same registry storage, so the pushed image resolves at the public name. Co-Authored-By: Claude Opus 4.8 --- .gitea/workflows/deploy-verso.yml | 8 ++++++-- 1 file changed, 6 insertions(+), 2 deletions(-) diff --git a/.gitea/workflows/deploy-verso.yml b/.gitea/workflows/deploy-verso.yml index 037deb8148..acba91b498 100644 --- a/.gitea/workflows/deploy-verso.yml +++ b/.gitea/workflows/deploy-verso.yml @@ -225,7 +225,11 @@ jobs: spec: containers: - name: verso - image: registry.git.svc.cluster.local:5000/verso:latest + # Pull via the public address: the cluster nodes' containerd + # is configured for registry.alocoq.fr, not the in-cluster + # service name. Both front the same registry storage, so the + # image pushed via the in-cluster address resolves here too. + image: registry.alocoq.fr/verso:latest ports: - containerPort: 80 env: @@ -257,7 +261,7 @@ jobs: - name: Deploy Verso image run: | kubectl -n test set image deployment/verso \ - verso=registry.git.svc.cluster.local:5000/verso:latest + verso=registry.alocoq.fr/verso:latest kubectl -n test rollout restart deployment/verso kubectl -n test rollout status deployment/verso --timeout=300s