This message was deleted.
# rancher-desktop
a
This message was deleted.
w
guessing minikube was the cluster in your .kube/config
or the context
take a look at your config and remove the sections or use
kubectl config
to look at existing config and use the rancher-desktop context
g
I did remove that but still the same, but also removed the whole config file and regenerated it, but still the same.
w
may be that its in as an alias. what does
where kubectl
show you?
g
Ah, thanks, will look there, this is my config file content
Copy code
apiVersion: v1
kind: Config
clusters:
  - name: rancher-desktop
    cluster:
      server: <https://127.0.0.1:6443>
      certificate-authority-data: SOME DATA
      insecure-skip-tls-verify: false
users:
  - name: rancher-desktop
    user:
      client-certificate-data: SOMEDATA
      client-key-data: SOME DATA
contexts:
  - name: rancher-desktop
    context:
      cluster: rancher-desktop
      name: rancher-desktop
      user: rancher-desktop
preferences: {}
current-context: rancher-desktop
w
you can type
alias
as well and i think that should show if its an active alias
yup config looks good. guessing minikube creates an alias, but been a very long time since i needed to go that path
g
yep!!!!! You've hit the nail on the head!!!! Well done and massive thank you!! I didn't think to look there - it's an alias with minikube in it!!! Thank you soooo much!!
👍 1
All working now! Thank you thank you
w
maybe a good health check for RD for all those Rancher folks watching.