-
Notifications
You must be signed in to change notification settings - Fork 623
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
node-problem-detector does not work if I change kubelet hostname to node ip. #23
Comments
@wangyumi Node problem detector also needs a
node-problem-detector needs to use the |
@wangyumi It seems that kube-proxy also has the problem if you don't manually change salt to override the hostname. Does kube-proxy work in your cluster after you override the hostname? :) |
meet the same issue:
I modify the unit file of kubeadm:
but it does not work... |
furthermore, it always dial tcp port 6443, but this port is not listening. |
I am running k8s 1.3.0 and with docker image node-problem-detector:v0.1
I changed kubelet --hostname-override with node ip on ehch minion:
when I start node-problem-detector as a daemon set, I got a lot of error messages:
It seems node-problem-detector still use the original os hostname to access node instead of overrided hostname that is registered in etcd.
/wangyumi
The text was updated successfully, but these errors were encountered: