This message was deleted.
# general
a
This message was deleted.
w
Do you have the KUBECONFIG env var set?
l
nope
w
Do you use a non-standard kubectl, e.g. shipped with your old setup or something? You can also do
kubectl config view
to checkout the kubeconfig kubectl is using
l
it is indeed using the correct config and does not have minikube anywhere inside of it.
I am not sure if I am using a non-standard kubectl but I dont think this is a kubectl issues, rather dont understand where minikube server is being invoked from.
w
It's surely unrelated to k3d though. Does
type kubectl
show you any info? E.g. an alias setting a different context?
l
@wide-garage-9465 this is an extremely late reply, but I had found that I had an alias which called the minikube command upon typing in kubectl
👍 1
Just thought I will mention it here, so that next time someone comes with a similar query, you can check for those as well.