apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
  name: queue-ingress
  namespace: alaska
  annotations:
    traefik.ingress.kubernetes.io/router.middlewares: alaska-common-cors@kubernetescrd
    traefik.ingress.kubernetes.io/router.tls: "true"
    # Cert resolver if you have it configured globally in Traefik (usually k3s-provided)
    # traefik.ingress.kubernetes.io/router.tls.certresolver: "letsencrypt"
spec:
  rules:
  - host: queue.workolik.com
    http:
      paths:
      - path: /
        pathType: Prefix
        backend:
          service:
            name: deliveries-service
            port:
              number: 8000
---
apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
  name: nearle-ingress
  namespace: nearle
  annotations:
    traefik.ingress.kubernetes.io/router.tls: "true"
spec:
  rules:
  - host: jupiter.nearle.app
    http:
      paths:
      - path: /
        pathType: Prefix
        backend:
          service:
            name: jupiter-cors-proxy
            port:
              number: 80
  - host: fiesta.nearle.app
    http:
      paths:
      # Real routing for this host is the standalone Docker/nginx proxy
      # (conf/nginx-fiesta.conf), which forwards everything to NodePort
      # 30823 (this backend, port 80) - no path splitting, no gateway
      # sidecar. This Ingress has no controller on the cluster (confirmed:
      # no Traefik/Envoy pod, no IngressClass) so it's inert either way,
      # but kept as a single correct catch-all rather than a stale
      # path-split that pointed part of it at a dead gateway sidecar.
      - path: /
        pathType: Prefix
        backend:
          service:
            name: fiesta
            port:
              number: 80
  - host: atlantis.nearle.app
    http:
      paths:
      - path: /
        pathType: Prefix
        backend:
          service:
            name: atlantis
            port:
              number: 80