Hi everyone, I just got into the monitoring section of the course, and now havin . . .

Yoni Zabari:
Hi everyone, I just got into the monitoring section of the course, and now having my cluster set up with minikube instead of docker-desktop (for ssh purposes).
In both scheduling and monitoring sections - mumshad uses kubectl within the node itself.
In order to run kubectl inside my node (created by minikube), I have installed the kubectl binary inside my node, but I guess that’s not enough as I get connection refused errors when trying to get pods, for example:
8916 memcache.go:265] couldn't get current server API group list: Get "<http://localhost:8080/api?timeout=32s>": dial tcp 127.0.0.1:8080: connect: connection refused

my question is - how do i configure kubectl inside my minikube node to recognize the cluster that it exists on?

Alistair Mackay:
You don’t have to run kubectl on the node. Minikube should have set up a KUBECONFIG so you can run it from your laptop’s shell.
kubectl is a network application. It doesn’t matter where you run it from as long as it has a route to the API server endpoint.

Yoni Zabari:
Thank you @Alistair Mackay :pray: