sreenath natarajan:
vagrant@kubenode01:~$ kubectl get pods
W0712 11:42:14.739793 15299 loader.go:222] Config not found: /etc/kubernetes/admin.conf
E0712 11:42:14.748217 15299 memcache.go:265] couldn’t get current server API group list: Get “http://localhost:8080/api?timeout=32s”: dial tcp [::1]:8080: connect: connection refused
E0712 11:42:14.749861 15299 memcache.go:265] couldn’t get current server API group list: Get “http://localhost:8080/api?timeout=32s”: dial tcp [::1]:8080: connect: connection refused
E0712 11:42:14.752167 15299 memcache.go:265] couldn’t get current server API group list: Get “http://localhost:8080/api?timeout=32s”: dial tcp [::1]:8080: connect: connection refused
E0712 11:42:14.754848 15299 memcache.go:265] couldn’t get current server API group list: Get “http://localhost:8080/api?timeout=32s”: dial tcp [::1]:8080: connect: connection refused
E0712 11:42:14.755893 15299 memcache.go:265] couldn’t get current server API group list: Get “http://localhost:8080/api?timeout=32s”: dial tcp [::1]:8080: connect: connection refused
The connection to the server localhost:8080 was refused - did you specify the right host or port?
vagrant@kubenode01:~$
Tej Singh Rana:
Hi @sreenath natarajan,
You need to run the kubectl command from the master node where you have set up the kubeconfig file.
sreenath natarajan:
hi @Tej Singh Rana,
sreenath natarajan:
Thanks for your input.
sreenath natarajan:
in real world, does end user have access to worker node? I believe everything will be done from kubctl which is actually running in master
Alistair Mackay:
In the real world, nobody but system administrators have access to the nodes, and you would normally be running kubectl from your own workstation, not any of the nodes.
If it’s a managed cluster like EKS, AKS or GKE you don’t even have access to the control plane nodes even with full admin permissions on your cloud account.