Ingress pathType=ImplementationSpecific causes issues with certain ingresses

[B0bby31]

Hi, I tried to deploy this helm chart on my cluster, but quickly ran into an issue with the ingress resource. I use the cilium ingress and it treats pathType=ImplementationSpecific as Exact, causing the Ingress resource to not work as intended (see cilium/cilium#30071). There are two fixes for this either change the pathType to Prefix or allow the user to change it in values.yaml.

[paimonsoror]

YES - ran into this same bug. Thanks for bringing this up!

[ashtonian]

What was the behavior you guys were seeing? Using cilium with nginx, kube-vip on a a rke2 cluster and when I try to log into pihole it seems to load the login page repeatedly. Seems to be resolved with replica count of 1..

[paimonsoror]

What was the behavior you guys were seeing? Using cilium with nginx, kube-vip on a a rke2 cluster and when I try to log into pihole it seems to load the login page repeatedly. Seems to be resolved with replica count of 1..

For me it was that I would land at the front door (in my case pihole.homelab) and then it would redirect me to pihole.homelab/admin (which told me that lighttpd was working with the virtualhost i set). The admin page however would have a 404 status code. Changing the pathType to Prefix took care of it for me. I only have a rep of 1 in my deployment

[youngnick]

The problem here is that, while ingress-nginx defines ImplementationSpecific path as meaning the same as Prefix, it doesn't have to, and Cilium's Ingress support has ImplementationSpecific mean "Regex match" instead. Using ImplementationSpecific when you mean Prefix match is not guaranteed to work with every Ingress implementation. Way better to use Prefix instead, which has a defined behavior, and conformance tests to validate it.