# vikunja.aleshym.co is PRIVATE, exactly like vault.aleshym.co. It is deliberately
# absent from the k3s `catchall-to-docker-apps` public host list and from the Docker
# Traefik `wan` entrypoint, so the internet has no route to it. Pi-hole resolves the
# name to 10.10.0.100 (the k3s node / Traefik external IP) for LAN/VPN clients.
# Traffic: client -> vikunja.aleshym.co -> 10.10.0.100 -> Traefik -> vikunja service
#          -> vikunja pod:3456
apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
  name: vikunja
  namespace: vikunja
  annotations:
    cert-manager.io/cluster-issuer: letsencrypt-prod
    traefik.ingress.kubernetes.io/router.entrypoints: websecure
spec:
  ingressClassName: traefik
  rules:
    - host: vikunja.aleshym.co
      http:
        paths:
          - path: /
            pathType: Prefix
            backend:
              service:
                name: vikunja
                port:
                  name: http
  tls:
    - hosts:
        - vikunja.aleshym.co
      secretName: vikunja-tls