# Exposes VNCmail+ at vncmail.sandbox.vnc.de, alongside bulwark.sandbox.vnc.de.
# MATCH YOUR CLUSTER — inspect the existing Bulwark ingress and copy its
# ingressClassName + TLS/cert-manager annotations:
#   kubectl get ingress -A | grep bulwark
#   kubectl get ingress <bulwark-ingress> -n <ns> -o yaml
apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
  name: vncmail-plus
  namespace: vncmail
  annotations:
    # cert-manager issuer — set to whatever bulwark.sandbox.vnc.de uses.
    cert-manager.io/cluster-issuer: letsencrypt-prod
    # Mail attachments can be large; raise the nginx body limit.
    nginx.ingress.kubernetes.io/proxy-body-size: "100m"
spec:
  # microk8s ingress addon class is usually "public" (nginx). Confirm with
  # `kubectl get ingressclass` and match bulwark's.
  ingressClassName: public
  tls:
    - hosts:
        - vncmail.sandbox.vnc.de
      secretName: vncmail-plus-tls
  rules:
    - host: vncmail.sandbox.vnc.de
      http:
        paths:
          - path: /
            pathType: Prefix
            backend:
              service:
                name: vncmail-plus
                port:
                  number: 80