payload: {"action":"opened","issue":{"url":"https://api.github.com/repos/kubernetes/ingress-nginx/issues/3742","repository_url":"https://api.github.com/repos/kubernetes/ingress-nginx","labels_url":"https://api.github.com/repos/kubernetes/ingress-nginx/issues/3742/labels{/name}","comments_url":"https://api.github.com/repos/kubernetes/ingress-nginx/issues/3742/comments","events_url":"https://api.github.com/repos/kubernetes/ingress-nginx/issues/3742/events","html_url":"https://github.com/kubernetes/ingress-nginx/issues/3742","id":408015671,"node_id":"MDU6SXNzdWU0MDgwMTU2NzE=","number":3742,"title":"Route handling in ingress when service has a context","user":{"login":"Ramk22","id":33617125,"node_id":"MDQ6VXNlcjMzNjE3MTI1","avatar_url":"https://avatars3.githubusercontent.com/u/33617125?v=4","gravatar_id":"","url":"https://api.github.com/users/Ramk22","html_url":"https://github.com/Ramk22","followers_url":"https://api.github.com/users/Ramk22/followers","following_url":"https://api.github.com/users/Ramk22/following{/other_user}","gists_url":"https://api.github.com/users/Ramk22/gists{/gist_id}","starred_url":"https://api.github.com/users/Ramk22/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/Ramk22/subscriptions","organizations_url":"https://api.github.com/users/Ramk22/orgs","repos_url":"https://api.github.com/users/Ramk22/repos","events_url":"https://api.github.com/users/Ramk22/events{/privacy}","received_events_url":"https://api.github.com/users/Ramk22/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":0,"created_at":"2019-02-08T05:50:22Z","updated_at":"2019-02-08T05:50:22Z","closed_at":null,"author_association":"NONE","body":"<!-- Thanks for filing an issue! Before hitting the button, please answer these questions.-->\r\n\r\n**Is this a request for help?** (If yes, you should use our troubleshooting guide and community support channels, see https://kubernetes.io/docs/tasks/debug-application-cluster/troubleshooting/.):\r\nYes\r\n\r\n**What keywords did you search in NGINX Ingress controller issues before filing this one?** (If you have found any duplicates, you should instead reply there.):\r\nKubernetes ingress, ingress routing when service has a context\r\n\r\n---\r\n\r\n**Is this a BUG REPORT or FEATURE REQUEST?** (choose one):\r\n\r\n<!--\r\nIf this is a BUG REPORT, please:\r\n  - Fill in as much of the template below as you can.  If you leave out\r\n    information, we can't help you as well.\r\n\r\nIf this is a FEATURE REQUEST, please:\r\n  - Describe *in detail* the feature/behavior/change you'd like to see.\r\n\r\nIn both cases, be ready for followup questions, and please respond in a timely\r\nmanner.  If we can't reproduce a bug or think a feature already exists, we\r\nmight close your issue.  If we're wrong, PLEASE feel free to reopen it and\r\nexplain why.\r\n-->\r\n\r\n**NGINX Ingress controller version**: v1beta1\r\n\r\n\r\n\r\n**Kubernetes version** (use `kubectl version`): 1.12.4\r\n\r\n\r\n**Environment**:\r\n\r\n- **Cloud provider or hardware configuration**: Azure Kubernetes Service\r\n- **OS** (e.g. from /etc/os-release):\r\n- **Kernel** (e.g. `uname -a`):\r\n- **Install tools**:\r\n- **Others**:\r\n\r\n\r\n**What happened**:\r\nI have 3 services running in the cluster, app dashboard, api and grafana. Ingress is configured in such a way that '/' would show the dashboard (service runs at port 80), '/api' would show the api endpoints (service at port 8000).\r\n\r\nNow I installed Prometheus,  that has grafana dashboard at port 3000. It works such that when I go to <IP Address>:3000 it would auto redirect to <IP Address>:3000/login.\r\n\r\nWhen I try to include this grafana dashboard with ingress (say at /monitor), it wouldn't route. Says,\r\n\r\nERROR Error: Uncaught (in promise): Error: Cannot match any routes. URL Segment: 'login'\r\nError: Cannot match any routes. URL Segment: 'login'\r\n\r\n**What you expected to happen**:\r\n'/monitor' brings up the grafana dashboard\r\n\r\n**How to reproduce it** (as minimally and precisely as possible):\r\nAdd any service to the ingress that has sub context running at any port other than 80, 443.\r\neg: When you go to that service <IP Address>:3000 it auto redirects to <IP Address>:3000/login.\r\n\r\n\r\n**Anything else we need to know**:\r\nLet me know if you need any further info. Thank you"}}
other: {"actor":{"display_login":"Ramk22"}}