harbor ingress fix

This commit is contained in:
Mukul Sharma
2026-08-31 14:40:18 +05:30
parent f7e37d18b4
commit 944ba711e2
+37 -5
View File
@@ -1,9 +1,13 @@
# Harbor's chart has no multi-host mechanism at all (checked against the
# actual template — no extraHosts like argo-cd, no secondaryingress like
# jenkins). This is a standalone second Ingress routing the Tailscale
# hostname to the same backend the chart's own Ingress uses
# (harbor-core:80) — confirmed against the real rendered Service, not
# assumed.
# jenkins), so this is a standalone second Ingress for the Tailscale
# hostname. Correction from an earlier version of this file: it routed
# everything to harbor-core alone. That's wrong — harbor-core is the
# API/auth backend; the actual web UI (the portal you log into) is served
# by harbor-portal. Mirrors the chart's own generated Ingress path split
# exactly (confirmed against its real rendered spec, not assumed this
# time): /api/, /service/, /v2/, /c/ go to harbor-core, everything else
# goes to harbor-portal.
apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
@@ -15,10 +19,38 @@ spec:
- host: "harbor.100.90.248.118.nip.io"
http:
paths:
- path: /
- path: /api/
pathType: Prefix
backend:
service:
name: harbor-core
port:
number: 80
- path: /service/
pathType: Prefix
backend:
service:
name: harbor-core
port:
number: 80
- path: /v2/
pathType: Prefix
backend:
service:
name: harbor-core
port:
number: 80
- path: /c/
pathType: Prefix
backend:
service:
name: harbor-core
port:
number: 80
- path: /
pathType: Prefix
backend:
service:
name: harbor-portal
port:
number: 80