Prior to applying Kubernetes Services, it is important to verify whether all nodes in the system are running kube-proxy. The daemon kube-proxy works as a network proxy in a node. It helps to reflect Service settings, such as IPs or ports on each node, and to do network forwarding. To check if kube-proxy is running or not, we take a look at network connections:

// check by command netstat with proper tags for showing the information we need, t:tcp, u:udp, l:listening, p:program, n:numeric address
// use root privilege for grabbing all processes
$ sudo netstat -tulpn | grep kube-proxy
tcp        0      0 127.0.0.1:10249         0.0.0.0:*               LISTEN      2326/kube-proxy
tcp6       0      0 :::31723                :::*                    LISTEN      2326/kube-proxy
tcp6       0      0 :::10256                :::*                    LISTEN      2326/kube-proxy

Once you see the output, the process ID 2326, kube-proxy, listening on port 10249 on localhost, the node is ready for Kubernetes Services. Go ahead and verify whether all of your nodes in the Kubernetes cluster having kube-proxy running on them.