mirror of
https://gitlab.kube.huskypup.net/Scooby/Homelabv4.git
synced 2026-08-21 05:26:49 +00:00
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 <noreply@anthropic.com>
43 lines
1.2 KiB
YAML
43 lines
1.2 KiB
YAML
---
|
|
# Real GitLab on the VPS. https-redirect Middleware from the start this
|
|
# time - see infrastructure/vps-standby/vault/manifests/ingress.yaml for
|
|
# why it's needed (found live 2026-08-21: Traefik serves plain HTTP
|
|
# alongside HTTPS unless explicitly redirected, which silently breaks
|
|
# OIDC login since the callback URL computed client-side won't match
|
|
# what's registered in Authentik).
|
|
apiVersion: traefik.io/v1alpha1
|
|
kind: Middleware
|
|
metadata:
|
|
name: https-redirect
|
|
namespace: gitlab
|
|
spec:
|
|
redirectScheme:
|
|
scheme: https
|
|
permanent: true
|
|
---
|
|
apiVersion: networking.k8s.io/v1
|
|
kind: Ingress
|
|
metadata:
|
|
name: vps-gitlab
|
|
namespace: gitlab
|
|
annotations:
|
|
cert-manager.io/cluster-issuer: letsencrypt-production
|
|
traefik.ingress.kubernetes.io/router.middlewares: gitlab-https-redirect@kubernetescrd
|
|
spec:
|
|
ingressClassName: traefik
|
|
tls:
|
|
- hosts:
|
|
- gitlab.vps.huskypup.net
|
|
secretName: vps-gitlab-tls
|
|
rules:
|
|
- host: gitlab.vps.huskypup.net
|
|
http:
|
|
paths:
|
|
- path: /
|
|
pathType: Prefix
|
|
backend:
|
|
service:
|
|
name: vps-gitlab-webservice-default
|
|
port:
|
|
number: 8181
|