-
Notifications
You must be signed in to change notification settings - Fork 221
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
Local l5d discovery issue in k8s-daemonset example #45
Comments
Thanks for the report! Bummer that |
I ran into this issue today too, and verified that it's still a problem with the latest version of Minikube. I added some extra information to our README to hopefully help clarify -- #109. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When I tried to deploy
k8s-daemonset/k8s/hello-world-1_4.yml
in my minikube I ran into an issue where the value given tospec.nodeName
(minikube
) wasn't resolvable by kube-dns, causing an exception inhello.py
. I'm not sure why this wasn't a problem in other k8s deployments. In minikube and k8s 1.4,hostIP.sh
or similar approach looking upstatus.hostIP
may still be necessary.There is a proposal in kubernetes to improve node-local service discovery when using DaemonSets that could solve this issue.
The text was updated successfully, but these errors were encountered: