CHORE(traefik): split centralized ingress

- management to per-applicati...
- Moved ArgoCD ingress to argocd/ingress/
- Moved Velero ingress to velero/ingress/
- Removed centralized ingress/ingresses.yaml (single point of failure)
- Updated root kustomization.yaml to reference argocd and velero
  directories
- Each application now manages its own ingress independently

velero/ingress/velero-ui-ingress.yaml

@@ -0,0 +1,24 @@
+apiVersion: networking.k8s.io/v1
+kind: Ingress
+metadata:
+  name: velero-ui-ingress
+  namespace: velero
+  annotations:
+    cert-manager.io/cluster-issuer: letsencrypt-prod
+spec:
+  ingressClassName: haproxy
+  tls:
+    - hosts:
+        - velero0213.kro.kr
+      secretName: velero-ui-tls
+  rules:
+    - host: velero0213.kro.kr
+      http:
+        paths:
+          - path: /
+            pathType: Prefix
+            backend:
+              service:
+                name: velero-ui
+                port:
+                  number: 3000

velero/kustomization.yaml

@@ -7,3 +7,4 @@ resources:
 
   # Velero credentials from Vault
   - external-secret.yaml
+  - ingress/velero-ui-ingress.yaml