-
Notifications
You must be signed in to change notification settings - Fork 1.7k
Ingress Not Forwarding to sub routes #935
Comments
@aledbf cool...when will the new container show up? Is there a place to find a list of these ingress containers? I had to ask in the git issues here to find out that this |
Yep you can find out from https://github.com/kubernetes/contrib/blob/master/ingress/controllers/nginx/Makefile#L4 what the lastest is. We'll move Ingress out into a seperate repo and at that point should do more regular releases. Can we close this out? |
Yes, thanks. |
I dont think this issue is fixed in #898 or maybe it is another issue. I have recompiled and created a new ingress with the code from master. I can see the change of the re-ordering of the location routes putting the Here is my ingress config. Using the real one this time (changed the domain name)
All routes except for Not getting why and trying to troubleshoot i copied the nginx.conf file that the ingress generates and loaded it up locally into the nginx container on docker hub:
With this i can get to all three routes. So this is even more odd to me on why it does work in the kube pod while it works locally. It is basically the same nginx.conf. I even tried with the container nginx container ive built for the kube and it works also. Hopefully someone that knows nginx better than I do can see the what is wrong here. Here is the nginx.conf file from my kube pod that i used locally. I had to remove some of the directives like the vhost status modules and the custom error routes b/c it is not loaded into the nginx container i downloaded from Docker hub.
This is how i test it out locally and when Kube launches it:
|
Sorry to resurrect the dead here, but is there a way that we can get this new nginx-ingress-controller image built? The pull request has been merged into master for a while. |
If there's an image later than 0.61 please update the makefile and I can push it. |
I am using this Ingress
gcr.io/google_containers/nginx-ingress-controller:0.61
and it is not forwarding to sub routes such as/eventData
or/api/v1/sdkErrors
. Those routes are returning the default 404 backend. However the root / route works.Ingress yaml
nginx.conf in the ingress pod:
The text was updated successfully, but these errors were encountered: