Is this a BUG REPORT or FEATURE REQUEST? (choose one): BUG REPORT
Please provide the following details:
Environment:
Minikube version (use minikube version): v0.25.0
cat ~/.minikube/machines/minikube/config.json | grep DriverName): hypervcat ~/.minikube/machines/minikube/config.json | grep -i ISO or minikube ssh cat /etc/VERSION): file://C:/Users/*/.minikube/cache/iso/minikube-v0.25.1.isoWhat happened:
Following along with https://medium.com/@Oskarr3/setting-up-ingress-on-minikube-6ae825e98f82. At the end, http://cheese.all/cheddar and http://cheese.all/stilton give 404 errors.
What you expected to happen:
http://cheese.all/cheddar and http://cheese.all/stilton should be 200 OK.
How to reproduce it (as minimally and precisely as possible):
minikube service stilton-cheeseecho "$(minikube ip) cheeses.all" | sudo tee -a /etc/hostshttp://cheeses.all/cheddar and see a 404Output of minikube logs (if applicable):
Anything else do we need to know:
v0.24.1 works correctly. I am _very_ new to kubernetes, so it could be a simple change in ingress that I am not aware of.
I'm experiencing similar issues. I just upgraded from k8s 1.8 to 1.9 via minikube v0.25.0 and ingress rules that worked before are no longer working
@mlschneid I've found at least 2 variations on what the annotation is supposed to be - try specifying both of the following...
ingress.kubernetes.io/rewrite-target: /
nginx.ingress.kubernetes.io/rewrite-target: /
I have the same Issue with minikube 0.25 and Kubernetes 1.9.0
@mellowplace Thanks, nginx.ingress.kubernetes.io/rewrite-target: / solved it for me.
@mellowplace I'll try that out this weekend and report back.
@mycrEEpy I had the same problem with Kubernetes 1.9 using weavenet. I switched to flannel and the problem went away. Not sure what minikube uses under the hood.
Thanks... This resolves the issue for 1.9
Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close.
Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale
/close
Most helpful comment
@mlschneid I've found at least 2 variations on what the annotation is supposed to be - try specifying both of the following...