From d99ebca8295acfe382143673b2074d4d7c251908 Mon Sep 17 00:00:00 2001 From: Hermes Agent service account Date: Thu, 4 Jun 2026 23:16:06 -0500 Subject: [PATCH] Add external-dns annotations to Harbor Ingress 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. --- cluster/platform/harbor/values.yaml | 2 ++ 1 file changed, 2 insertions(+) diff --git a/cluster/platform/harbor/values.yaml b/cluster/platform/harbor/values.yaml index 0aa2fcf..06c9e98 100644 --- a/cluster/platform/harbor/values.yaml +++ b/cluster/platform/harbor/values.yaml @@ -25,6 +25,8 @@ expose: cert-manager.io/cluster-issuer: letsencrypt-prod nginx.ingress.kubernetes.io/ssl-redirect: "true" 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 harborAdminPassword: ""