fix(harbor): switch from Gateway API to nginx-ingress

- Change expose.type from clusterIP to ingress
- Use nginx IngressClass
- Reference harbor-tls certificate secret
- Add staging cert-manager annotation
- Gateway API was returning intermittent 503 errors for static assets

cluster/platform/harbor/values.yaml

@@ -7,17 +7,24 @@
 # External URL for Harbor - primary DNS name
 externalURL: https://the-seas.local.mk-labs.cloud
 
-# Expose Harbor via ClusterIP (Gateway API handles ingress)
-# TLS termination handled by Gateway API, not Harbor
+# Expose Harbor via Ingress (nginx-ingress controller)
 expose:
-  type: clusterIP
+  type: ingress
   tls:
-    enabled: false
-  clusterIP:
-    name: the-seas
-    ports:
-      httpPort: 80
-      httpsPort: 443
+    enabled: true
+    certSource: secret
+    secret:
+      secretName: harbor-tls
+      notarySecretName: harbor-tls
+  ingress:
+    hosts:
+      core: the-seas.local.mk-labs.cloud
+      notary: notary-the-seas.local.mk-labs.cloud
+    className: nginx
+    annotations:
+      cert-manager.io/cluster-issuer: letsencrypt-staging
+      nginx.ingress.kubernetes.io/ssl-redirect: "true"
+      nginx.ingress.kubernetes.io/proxy-body-size: "0"
 
 # Admin credentials from ExternalSecret
 harborAdminPassword: ""