Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Local l5d discovery issue in k8s-daemonset example #45

Open
sevein opened this issue Oct 29, 2016 · 2 comments
Open

Local l5d discovery issue in k8s-daemonset example #45

sevein opened this issue Oct 29, 2016 · 2 comments

Comments

@sevein
Copy link
Contributor

sevein commented Oct 29, 2016 •
edited
Loading

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 to spec.nodeName (minikube) wasn't resolvable by kube-dns, causing an exception in hello.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 up status.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.
@adleong
Copy link
Member

adleong commented Oct 31, 2016 •
edited
Loading

Thanks for the report! Bummer that nodeName doesn't work in minikube.

@klingerf klingerf mentioned this issue Mar 9, 2017
Merged
@klingerf
Copy link
Contributor

klingerf commented Mar 9, 2017

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
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@klingerf @sevein @adleong