I set up Kong locally (Docker) with Nokia’s oidc plugin and used Auth0 as the OIDC authority – it worked wonderfully well!
I’ve since moved an identical service into Kubernetes using dist-kubernetes. I exposed the ingress-data-plane via Load Balancer and set an A record for the LB’s IP. The kong service’s route points to a deployment’s ClusterIP service and the host is the A record.
For some reason, Kong is bypassing the OIDC plugin and is routing straight to the deployment without authentication. Any ideas how I’d go about debugging?