Minikube: Error kubeconfig status: Kubeconfig does not have a record of the machine cluster

Created on 28 Mar 2019  路  7Comments  路  Source: kubernetes/minikube



minikube status

E0328 20:30:50.419672    4841 status.go:104] Error kubeconfig status: Kubeconfig does not have a record of the machine cluster
host: Running
kubelet: Running
apiserver: Running
kubectl: Misconfigured: pointing to stale minikube-vm.
To fix the kubectl context, run minikube update-context


Fedora 29 was used with latest minikube 1.0.0

help wanted kinsupport prioritbacklog 2019q2

Most helpful comment

Closing. The basic issue here is that kubectl and minikube only know about the clusters started by the user: if you use sudo, that's root.

To prevent confusion, minikube v1.4 will exit if you try to use something other than the none driver as root.

All 7 comments

Hi, did you try running minikube update-context?

AFAIK, this error message should never happen. I'm really curious what's going on here.

ditto for me on fedora 29:

$ uname -a
Linux localhost.localdomain 4.19.7-300.fc29.x86_64 #1 SMP Wed Dec 5 22:21:07 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
$ mk version
minikube version: v1.0.1
$ mk update-context

馃挘  update config: Kubeconfig does not have a record of the machine cluster

$ mk status
E0430 16:12:22.678686   18626 status.go:110] Error kubeconfig status: Kubeconfig does not have a record of the machine cluster
host: Running
kubelet: Running
apiserver: Running
kubectl: Misconfigured: pointing to stale minikube-vm.
To fix the kubectl context, run minikube update-context

@jeffvance - What happens if you type:

grep -- "- name" ~/.kube/config

I'm reaching here - but was the VM started using another user like via sudo by any chance?

@tstromberg :

$ grep -- "- name" ~/.kube/config
- name: kubernetes-admin
- name: minikube

But it seems to be working now. I stopped it, rm'd all in _~/.minikube_ and reran the minikube start --vm-driver=kvm2

How did you start the minikube?
I have run

sudo minikube start

And when I run minikube status, it report the same error.
sudo minikube status solved the problem

Closing. The basic issue here is that kubectl and minikube only know about the clusters started by the user: if you use sudo, that's root.

To prevent confusion, minikube v1.4 will exit if you try to use something other than the none driver as root.

Was this page helpful?
0 / 5 - 0 ratings

Related issues

Starefossen picture Starefossen  路  3Comments

djschny picture djschny  路  3Comments

ahmetb picture ahmetb  路  3Comments

StasPerekrestov picture StasPerekrestov  路  3Comments

RaeesBhatti picture RaeesBhatti  路  3Comments