path based routing is not working
vanielathor opened this issue · 3 comments
`apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
name: ingress-quicklinks-redirect
namespace: testing
annotations:
cert-manager.io/issuer: "letsencrypt-prod-promsite"
ingress.kubernetes.io/service-upstream: "true"
kubernetes.io/ingress.class: "nginx"
kubernetes.io/tls-acme: "true"
nginx.ingress.kubernetes.io/app-root: "/quicklinks"
nginx.ingress.kubernetes.io/proxy-body-size: 3g
nginx.ingress.kubernetes.io/rewrite-target: "/"
spec:
tls:
- hosts:
- bar.testing.com
secretName: letsencrypt-cert-promsite
rules:
- host: bar.testing.com
http:
paths:
- pathType: Prefix
path: "/coffee"
backend:
service:
name: service-a
port:
number: 8050
- pathType: ImplementationSpecific
path: "/"
backend:
service:
name: service-b
port:
number: 8191
``
i am able to access service-b with bar.testing.com
unable to access service-b bar.testing.com/coffee
its showing empty webpage with 308 redirect in network logs
Ingress Nginx Controller Version:v1.11.1
helm chart version : 4.11.1
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-sigs/prow repository.
-
@vanielathor a new bug report has a template that asks questions. Since you have not provided answers to those questions, there is very little possibility to do any analysis and make comments based on data analysis.
-
In general path based routing works for every single user of the ingress-nginx controller so what error you are seeing is because of your config
-
Please look at the template of a new bug report and edit the description of this issue to answer the questions asked there
-
The little bit of info you posted is hardly readable because its not in markdown format. So ensure that you provide answers to the questions asked in the new bug report template, in markdown format.
-
You need to edit this issue description and do not create a new issue
-
In general the path / will match all requests so its possible that is your problem. But without all the answers to the questions in the new bug report template, its hard to tell.
-
Once you have posted the info requested, you can reopen this issue. I will close it for now as there is no action item to track for the project here.
/close
@longwuyuan: Closing this issue.
In response to this:
@vanielathor a new bug report has a template that asks questions. Since you have not provided answers to those questions, there is very little possibility to do any analysis and make comments based on data analysis.
In general path based routing works for every single user of the ingress-nginx controller so what error you are seeing is because of your config
Please look at the template of a new bug report and edit the description of this issue to answer the questions asked there
The little bit of info you posted is hardly readable because its not in markdown format. So ensure that you provide answers to the questions asked in the new bug report template, in markdown format.
You need to edit this issue description and do not create a new issue
In general the path / will match all requests so its possible that is your problem. But without all the answers to the questions in the new bug report template, its hard to tell.
Once you have posted the info requested, you can reopen this issue. I will close it for now as there is no action item to track for the project here.
/close
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-sigs/prow repository.