-
Notifications
You must be signed in to change notification settings - Fork 8.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Ingress path does not work #349
Comments
@gyliu513 |
Thanks @aledbf , yes, you may see that both of my service The following is the logs from ingress controller:
And my ingress version is |
@gyliu513 please remove |
So I need to use the latest version ingress? Does there are any link/issue that I can refer to get more detail for what do you fix? @aledbf |
@gyliu513 #121 |
Thanks @aledbf , will try to see if the latest build can help. But with my current env, after removing the Seems the ingress has some problems if I define a
|
@gyliu513 right, that output is from one of our nginx behind the ingress controller. Please keep in mind that if youmake a request to |
@aledbf finally, it is working now after I applied My whole yaml template:
And test result:
|
came into same problem. we should update online doc of ingress to add "annotations: ingress.kubernetes.io/rewrite-target: /" into example yaml |
@gyliu513 broken link |
I created a ingress service as following:
Then after the service create finished, I can see the detail of ingress is as following:
Then I put
9.111.253.118 mynginx.com
to the/etc/hosts
on which I will access the services, and then when I accessmynginx.com/v1
andmynginx.com/v2
, both failed.Then I check the
nginx conf
for the ingress controller, found the proxy setting is as following:For the
proxy_pass
, should not we useabsolute path
?I mean seems the proxy should be set as following:
The text was updated successfully, but these errors were encountered: