From ab084715e60b3e29cea37816d6c56060dc2e2385 Mon Sep 17 00:00:00 2001 From: Scooby Husky Date: Thu, 20 Aug 2026 22:47:48 -0500 Subject: [PATCH] Fix VPS GitLab ingress backend service name Ingress pointed at 'gitlab-webservice-default' but the chart release name on the VPS is 'vps-gitlab', so the actual Service Helm creates is 'vps-gitlab-webservice-default' (confirmed via 'kubectl get svc -n gitlab'). Home's GitLab isn't affected - it routes via Istio VirtualService, not this Ingress, and its release name has no prefix. This was the actual cause of the persistent 404 - webservice pod was healthy and passing readiness checks the whole time, Traefik just had no matching backend to route to. Co-Authored-By: Claude Sonnet 5 --- infrastructure/vps-standby/gitlab/manifests/ingress.yaml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/infrastructure/vps-standby/gitlab/manifests/ingress.yaml b/infrastructure/vps-standby/gitlab/manifests/ingress.yaml index dd7a793..3b43a05 100644 --- a/infrastructure/vps-standby/gitlab/manifests/ingress.yaml +++ b/infrastructure/vps-standby/gitlab/manifests/ingress.yaml @@ -37,6 +37,6 @@ spec: pathType: Prefix backend: service: - name: gitlab-webservice-default + name: vps-gitlab-webservice-default port: number: 8181