Rancher Desktop on MacOS - kubectl connection refused

Hi -

I’m attempting to run Rancher Desktop (v1.5.1) on MacOS Monterey (Intel silicon), and have everything running - I’m able to use Portainer to get helm charts running and use the kubectl command within portainer’s management interface without an issue.

But on the local machine, when I run kubectl, I get the following error: (cluster-info is what I asked for here)

I1007 11:49:13.782135   11742 versioner.go:58] Get "https://127.0.0.1:62258/version?timeout=5s": dial tcp 127.0.0.1:62258: connect: connection refused

To further debug and diagnose cluster problems, use 'kubectl cluster-info dump'.
The connection to the server 127.0.0.1:62258 was refused - did you specify the right host or port?

If I use the ‘k’ alias, I get:

I1007 11:50:10.522980   11955 versioner.go:58] Get "https://127.0.0.1:62258/version?timeout=5s": dial tcp 127.0.0.1:62258: connect: connection refused
I1007 11:50:10.634336   11956 versioner.go:58] Get "https://127.0.0.1:62258/version?timeout=5s": dial tcp 127.0.0.1:62258: connect: connection refused
Alias Expansion: kubectl cluster-info
    k8s Context: minikube
  k8s Namespace: default (to set, use kubens {namespace})
--------------------------------------
I1007 11:50:10.747059   11957 versioner.go:58] Get "https://127.0.0.1:62258/version?timeout=5s": dial tcp 127.0.0.1:62258: connect: connection refused

To further debug and diagnose cluster problems, use 'kubectl cluster-info dump'.
The connection to the server 127.0.0.1:62258 was refused - did you specify the right host or port?

It doesn’t seem that anything is listening on port 62258, but everything looks like it’s running fine.

Wondering what I’m missing - I had deleted the entire installation and reinstalled, along with removing ~/.kube entirely, so the config file that’s there was generated during startup and I haven’t modified it in any way. The containers that I’m looking to tweak with kubectl are in the default namespace, which is part of the minikube context/cluster, which seems to be what I can’t connect to.

Apologies if my terminology is wonky - I’m really new to kubernetes and still am learning.

ETA: It looks like this may be a remnant from a different/previous installation of something on the system - I’d like to get confirmation that that’s probably the case, but doing an install on a Linux desktop, I don’t see a ‘minikube’ context, just the ‘rancher-desktop’ context.

ETA #2: Confirmed it - this was cruft left over from a prior installation that was removed improperly. I’ve cleaned it up and everything’s working fine now.