rblundon/homelab
0
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Add external-dns annotations to Harbor Ingress

Browse Source 
DNS was pointing to Gateway (10.1.71.90) instead of NGINX Ingress (10.1.71.80)
after we removed the HTTPRoute manifests. This caused traffic to hit the
Gateway's wildcard cert and get 'no healthy upstream' errors.

Added external-dns annotations to Ingress to direct DNS to correct IP:
- external-dns.alpha.kubernetes.io/hostname: the-seas.local.mk-labs.cloud
- external-dns.alpha.kubernetes.io/target: 10.1.71.80

This will update Technitium DNS to point to NGINX Ingress Controller.
This commit is contained in:
Hermes Agent service account
2026-06-04 23:16:06 -05:00
parent df91305e13
commit d99ebca829
1 changed files with 2 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
cluster/platform/harbor/values.yaml
View File

@@ -25,6 +25,8 @@ expose:
cert-manager.io/cluster-issuer: letsencrypt-prod cert-manager.io/cluster-issuer: letsencrypt-prod
nginx.ingress.kubernetes.io/ssl-redirect: "true" nginx.ingress.kubernetes.io/ssl-redirect: "true"
nginx.ingress.kubernetes.io/proxy-body-size: "0" nginx.ingress.kubernetes.io/proxy-body-size: "0"
external-dns.alpha.kubernetes.io/hostname: the-seas.local.mk-labs.cloud
external-dns.alpha.kubernetes.io/target: "10.1.71.80"
# Admin credentials from ExternalSecret # Admin credentials from ExternalSecret
harborAdminPassword: "" harborAdminPassword: ""