-
Notifications
You must be signed in to change notification settings - Fork 59
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Issue with multiple nginx-ingress controllers #17
Comments
I know it's been a long time, did you find a solution? I'm stuck at this point. |
bernatvadell
added a commit
to bernatvadell/hairpin-proxy
that referenced
this issue
May 20, 2023
I think I ended up with a workaround: Switching which Ingress I was using for that particular service, to get to a compatible configuration. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Summary:
When there are multiple ingress controllers; for example, one with proxy-protocol enabled, and one without proxy protocol enabled, the hairpin proxy will make rewrite rules for all. But this gives 404 issues for the non-proxied ingresses.
Steps to reproduce:
kubectl get configmap -n kube-system coredns -o=jsonpath='{.data.Corefile}'
Suggested fix
Include the ingress class in the polling of ingress resources.
**Now I'm writing this, I realize this may be because I'm still on K8S 1.18, and it doesn't support the new ingress definitions (supporting ingress classes). Will need to test.
The text was updated successfully, but these errors were encountered: