:10255 is on a test server running microk8s snap:

root@nuc1:~# netstat -natp | grep kubelet
tcp        0      0 127.0.0.1:10248         0.0.0.0:*               LISTEN  
    4129/kubelet
tcp        0      0 127.0.0.1:37888         127.0.0.1:16443        
 ESTABLISHED 4129/kubelet
tcp6       0      0 :::10255                :::*                    LISTEN  
    4129/kubelet
tcp6       0      0 :::10250                :::*                    LISTEN  
    4129/kubelet
root@nuc1:~#

Looking at a production k8s 1.16 cluster (installed using kubectl) I don't 
see this port open.  And I'm afraid I don't know where it's configured, 
even in microk8s.

I do note that the kubelet command line includes "--insecure-port=0", but I 
don't think that's it; even with a reboot it comes up on the same ports.

-- 
You received this message because you are subscribed to the Google Groups 
"Prometheus Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/prometheus-users/c6b660db-d304-4e21-81ff-788ffd90ea18o%40googlegroups.com.

Reply via email to