NGINX Ingress controller version:

0.32.0

Kubernetes version (use kubectl version):

Client Version: version.Info{Major:"1", Minor:"18", GitVersion:"v1.18.2", GitCommit:"52c56ce7a8272c798dbc29846288d7cd9fbae032", GitTreeState:"clean", BuildDate:"2020-04-16T11:56:40Z", GoVersion:"go1.13.9", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"17+", GitVersion:"v1.17.9-eks-4c6976", GitCommit:"4c6976793196d70bc5cd29d56ce5440c9473648e", GitTreeState:"clean", BuildDate:"2020-07-17T18:46:04Z", GoVersion:"go1.13.9", Compiler:"gc", Platform:"linux/amd64"}

Environment:

• Cloud provider or hardware configuration: AWS EKS
• OS (e.g. from /etc/os-release): Amazon Linux 2
• Kernel (e.g. uname -a): 4.14.154-128.181.amzn2.x86_64
• Install tools: nginx-ingress in ingress-nginx and jupyter notenbook in application namespace
• Others:

What happened:

What you expected to happen:

I launched load balancer part of ingress-nginx. The use case is:-

When user launched a container it should expose jupyter service on clusterIP and accessible via ingress resource redirection on specific URL e.g. example.com//

The ingress resource rule is not redirecting properly.

How to reproduce it:

Create custom docker image with jupyter installed. Deploy ingress controller and ingress resources and access the jupyter through load balancer ingress resource url.

Anything else we need to know:

/kind bug