Using custom Ingress causing 404 error on authenticate service

[pavankumar-go]

    Using custom Ingress causing 404 error on authenticate service

"size":0,"response-code":404,"response-code-details":"route_not_found","time":"2022-10-13T06:58:16Z","message":"http-request"}

Ingress.yaml

apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
  name: custom-pomerium-ingress
  namespace: pomerium
spec:
  ingressClassName: nginx
  rules:
    - host: authenticate.dev.X.X
      http:
        paths:
          - backend:
              service:
                name: pomerium-authenticate
                port:
                  number: 80
            pathType: ImplementationSpecific
    - host: int-grafana.dev.X.X
      http:
        paths:
          - backend:
              service:
                name: pomerium-proxy
                port:
                  number: 80
            pathType: ImplementationSpecific

workaround: remove or set AUTHENTICATE_INTERNAL_SERVICE_URL to ""

  # we manage ingress on behalf of pomerium.
  # remove AUTHENTICATE_INTERNAL_SERVICE_URL from pomerium-authenticate.
  set {
    name  = "ingress.enabled"
    value = false
  }

  # workaround to fix 404 error in authenticate service
  set {
    name  = "extraEnv.AUTHENTICATE_INTERNAL_SERVICE_URL"
    value = ""
  }

Originally posted by @pavankumar-go in #277 (comment)

[abh]

I don't use a custom ingress, so I have

ingress:
  enabled: false

which makes AUTHENTICATE_INTERNAL_SERVICE_URL be set to the value (and causes the 404s, best I can tell).

[abh]

eh, I mean I use the ingressController so ingress is disabled.