Giter Club home page Giter Club logo

Comments (4)

Random-Liu avatar Random-Liu commented on June 27, 2024

@wangyumi Node problem detector also needs a hostname-overwrite flag. I'll add it soon.
Thanks for reporting the issue! :)

It seems node-problem-detector still use the original os hostname to access node instead of overrided hostname that is registered in etcd.

node-problem-detector needs to use the node name to access the resource in etcd to get the node name. There is an chicken-egg issue here.

from node-problem-detector.

Random-Liu avatar Random-Liu commented on June 27, 2024

@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? :)

from node-problem-detector.

KeithTt avatar KeithTt commented on June 27, 2024

meet the same issue:

Nov  2 05:48:49 uy05-13 kubelet[29322]: E1102 05:48:49.083813   29322 reflector.go:190] k8s.io/kubernetes/pkg/kubelet/kubelet.go:390: Failed to list *v1.Node: Get https://192.168.5.42:6443/api/v1/nodes?fieldSelector=metadata.name%3D192.168.5.42&resourceVersion=0: dial tcp 192.168.5.42:6443: getsockopt: connection refused
Nov  2 05:48:49 uy05-13 kubelet[29322]: E1102 05:48:49.281283   29322 reflector.go:190] k8s.io/kubernetes/pkg/kubelet/kubelet.go:382: Failed to list *v1.Service: Get https://192.168.5.42:6443/api/v1/services?resourceVersion=0: dial tcp 192.168.5.42:6443: getsockopt: connection refused

I modify the unit file of kubeadm:

Nov  2 05:48:49 uy05-13 kubelet[29322]: E1102 05:48:49.083813   29322 reflector.go:190] k8s.io/kubernetes/pkg/kubelet/kubelet.go:390: Failed to list *v1.Node: Get https://192.168.5.42:6443/api/v1/nodes?fieldSelector=metadata.name%3D192.168.5.42&resourceVersion=0: dial tcp 192.168.5.42:6443: getsockopt: connection refused
Nov  2 05:48:49 uy05-13 kubelet[29322]: E1102 05:48:49.281283   29322 reflector.go:190] k8s.io/kubernetes/pkg/kubelet/kubelet.go:382: Failed to list *v1.Service: Get https://192.168.5.42:6443/api/v1/services?resourceVersion=0: dial tcp 192.168.5.42:6443: getsockopt: connection refused

but it does not work...

from node-problem-detector.

KeithTt avatar KeithTt commented on June 27, 2024

furthermore, it always dial tcp port 6443, but this port is not listening.

from node-problem-detector.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.