fix(ingress): Add nginx LoadBalancer service to GitOps — removes 503 error

Remove manual nginx-controller-svc.yaml (duplicate with Helm-managed service).
Helm chart creates LoadBalancer service automatically. Manual manifest caused conflicts.

Ingress controller now solely managed by Helm chart values.

k8s/bootstrap/ingress/kustomization.yaml

@@ -1,7 +1,5 @@
 apiVersion: kustomize.config.k8s.io/v1beta1
 kind: Kustomization
 namespace: ingress-nginx
-resources:
+resources: []
-  - nginx-controller-svc.yaml
+# Ingress controller deployed via Helm chart
-# Ingress nginx controller pods deployed via Helm chart (in cluster)
-# LoadBalancer service defined here for GitOps management

k8s/bootstrap/ingress/nginx-controller-svc.yaml

@@ -1,30 +0,0 @@
-apiVersion: v1
-kind: Service
-metadata:
-  labels:
-    app.kubernetes.io/component: controller
-    app.kubernetes.io/instance: ingress-nginx
-    app.kubernetes.io/name: ingress-nginx
-    app.kubernetes.io/part-of: ingress-nginx
-    app.kubernetes.io/version: 4.11.1
-  name: ingress-nginx-controller
-  namespace: ingress-nginx
-spec:
-  allocateLoadBalancerNodePorts: true
-  externalTrafficPolicy: Local
-  ports:
-  - appProtocol: http
-    name: http
-    port: 80
-    protocol: TCP
-    targetPort: http
-  - appProtocol: https
-    name: https
-    port: 443
-    protocol: TCP
-    targetPort: https
-  selector:
-    app.kubernetes.io/component: controller
-    app.kubernetes.io/instance: ingress-nginx
-    app.kubernetes.io/name: ingress-nginx
-  type: LoadBalancer