CODEWITHSUNDEEP
kuberneteskubelet
Ryan
Ryan

Reputation: 1221

Cannot curl kubelet read-only port

I have a heapster pod running on one of the nodes in my Kubernetes cluster. It is able to get http://<node-with-heapster-pod>:10255/stats/summary just fine, but whenever it runs the same get request on another node, it cannot. When I run curl from within any given node I can access that port, but when I curl any node from another machine I get the following error:

Failed to connect to 128.180.120.229 port 10255: No route to host

The following is the netstat output for all ports on which the kubelet is listening:

netstat -ap | grep -i "listen" | grep "kubelet"
tcp        0      0 localhost:10248         0.0.0.0:*               LISTEN 7562/kubelet        
tcp6       0      0 [::]:4194               [::]:*                  LISTEN     7562/kubelet        
tcp6       0      0 [::]:10250              [::]:*                  LISTEN 7562/kubelet
tcp6       0      0 [::]:10255              [::]:*                  LISTEN      7562/kubelet      
unix  2      [ ACC ]     STREAM     LISTENING     621349   7562/kubelet       /var/run/dockershim.sock

I apologize for the messy last column. Any ideas why this may be? My iptables rules are set up to accept all incoming connections, and any node can ping port 10250 fine, just not 10255.

Upvotes: 0

Views: 1500

Answers (2)

ThePilot
ThePilot

Reputation: 53

If anybody still cares, port 10255 is the kubelet's read only port and may or may not be configured. You can confirm this by accessing the worker node in question then looking at the kubelet's startup command.

systemctl status kubelet-worker.service

Some on-prem kubernetes solutions set this to 0 as mentioned below

https://kubernetes.io/docs/reference/command-line-tools-reference/kubelet/

--read-only-port int32 The read-only port for the Kubelet to serve on with no authentication/authorization (set to 0 to disable) (default 10255) (DEPRECATED: This parameter should be set via the config file specified by the Kubelet's --config flag. See https://kubernetes.io/docs/tasks/administer-cluster/kubelet-config-file/ for more information.)

Upvotes: 0

sfgroups
sfgroups

Reputation: 19119

you may not have ip_forward enabled on your system. can you check this settings?

 sysctl -n net.ipv4.ip_forward

Upvotes: 0

Related Questions