4.5.0 upgrade caused one of my ingresses to start returning 404s #9623
Labels
kind/bug
Categorizes issue or PR as related to a bug.
needs-priority
needs-triage
Indicates an issue or PR lacks a `triage/foo` label and requires one.
What happened:
I upgraded from Helm Chart 4.4.2 to 4.5.0 this evening and got 404s from NginX instead of responses on one of my services. I have an automated monitor set up to attempt to reach a URL every minute and it reported the failure. I downgraded to 4.4.2 and the 404 went away. I upgraded again and the 404s came back.
What you expected to happen:
The new version did not properly translate my ingress configuration into its reverse proxy configuration.
NGINX Ingress controller version (exec into the pod and run nginx-ingress-controller --version.):
Kubernetes version (use
kubectl version
):Server Version: version.Info{Major:"1", Minor:"25", GitVersion:"v1.25.4", GitCommit:"872a965c6c6526caa949f0c6ac028ef7aff3fb78", GitTreeState:"clean", BuildDate:"2022-11-09T13:29:58Z", GoVersion:"go1.19.3", Compiler:"gc", Platform:"linux/amd64"}
Environment:
How to reproduce this issue:
Here's my ingress configuration that is breaking:
Anything else we need to know:
The text was updated successfully, but these errors were encountered: