Ingress resources not working after update from v1.8.1 to v1.9.4 (chart version v4.7.1 to v4.8.3)

[marino-u]

Hi, I have an ingress resource with path "/" and several ingresses for apis with path (for example "/api1", "/api2") etc.
The cluster is on EKS and after an upgrade of EKS cluster and nginx-controller from v1.8.1 to v1.9.4 (chart version v4.7.1 to v4.8.3), all the requests to "/api1", "/api2", ... are handled by the ingress at "/".
I attach the ingress resources configuration as a screenshot (sorry but I can't copy/paste text):

Do you have any idea on what the problem could be? Maybe there were some changes between the versions that i didn't found.
Thanks in advance for your help.

[k8s-ci-robot]

This issue is currently awaiting triage.

If Ingress contributors determines this is a relevant issue, they will accept it by applying the triage/accepted label and provide further guidance.

The triage/accepted label can be added by org members by writing /triage accepted in a comment.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[strongjz]

Read some of the considerations for 1.9.0 https://github.com/kubernetes/ingress-nginx/releases/tag/controller-v1.9.0

There were some changes that might effect your configurations.

[longwuyuan]

/kind support

[strongjz]

/triage more-information

There are only two ingresses shown, / and /wonder-src-auth , so /api would go to the /

Do you post all the ingresses?

Did you check the links https://github.com/kubernetes/ingress-nginx/releases/tag/controller-v1.9.0

[k8s-ci-robot]

@strongjz: The label(s) triage/more-information cannot be applied, because the repository doesn't have them.

In response to this:

/triage more-information

There are only two ingresses shown, / and /wonder-src-auth , so /api would go to the /

Do you post all the ingresses?

Did you check the links https://github.com/kubernetes/ingress-nginx/releases/tag/controller-v1.9.0

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[longwuyuan]

/triage needs-information

[marino-u]

@strongjz "/api" was just an example. I set up an environment to replicate the behaviour.
My idea is that ssl-redirect removes the trailing slash and the path is no more matched; in the following example default-app1-svc-80 is the service associated with /app1($|(/.*)) prefix, while default-app-svc-80 is the one associated with "/" prefix.
After 308 Permanent redirect, the request is sent to the wrong service:

Do you have any idea about that?

BRs,
Marino

[marino-u]

It seems that now, with the annotations validation, rewrite-prefix should always start with "/" .
I got the following error and I solved adding the slash before $1:
validation error on ingress wonder/wonder-src-authz-private-ingress: annotation rewrite-target contains invalid value $1