Fix: align ingress base and overlays - single host per environment

infrastructure/platform/networking/ingress/base/ingress.yaml

@@ -32,9 +32,6 @@ spec:
   tls:
   - hosts:
     - DOMAIN_PLACEHOLDER  # To be replaced by kustomize
-    - gitea.DOMAIN_PLACEHOLDER  # To be replaced by kustomize
-    - registry.DOMAIN_PLACEHOLDER  # To be replaced by kustomize
-    - mail.DOMAIN_PLACEHOLDER  # To be replaced by kustomize
     secretName: TLS_SECRET_PLACEHOLDER  # To be replaced by kustomize
   rules:
   # Main application routes
@@ -55,38 +52,7 @@ spec:
             name: gateway-service
             port:
               number: 8000
-  # Gitea CI/CD route
-  - host: gitea.DOMAIN_PLACEHOLDER  # To be replaced by kustomize
-    http:
-      paths:
-      - path: /
-        pathType: Prefix
-        backend:
-          service:
-            name: gitea-http
-            port:
-              number: 3000
-  # Gitea Container Registry route
-  # NOTE: Gitea's container registry is served on the same HTTP port (3000) under /v2/
-  # It does NOT run on a separate port - the registry.PORT config is not used for external access
-  - host: registry.DOMAIN_PLACEHOLDER  # To be replaced by kustomize
-    http:
-      paths:
-      - path: /
-        pathType: Prefix
-        backend:
-          service:
-            name: gitea-http  # Service created by Gitea Helm chart
-            port:
-              number: 3000  # Same as HTTP port - registry is at /v2/ path
-  # Mail server web interface (webmail and admin)
-  - host: mail.DOMAIN_PLACEHOLDER  # To be replaced by kustomize
-    http:
-      paths:
-      - path: /
-        pathType: Prefix
-        backend:
-          service:
-            name: mailu-front
-            port:
-              number: 80
+  # NOTE: Gitea and Registry ingresses are managed by Gitea Helm chart
+  # See infrastructure/cicd/gitea/values.yaml for ingress configuration
+  # NOTE: Mail ingress is deployed separately via mailu-helm resource
+  # to avoid 503 errors when Mailu is not running