minikube status kubectl entry always misconfigured for none driver

Created on 26 Jun 2017 · 7Comments · Source: kubernetes/minikube

For the minikube --vm-driver=none option, minikube status always shows that kubectl is misconfigured even when this is not the case. We should fix this so that the kubectl entry is correct for the none driver.

cnone-driver kinbug

Source

aaron-prindle

👍3

Most helpful comment

this seems to still be the case in v0.30.0 -- the status command reports that kubectl is misconfigured:

$ minikube status
minikube: Running
cluster: Running
kubectl: Misconfigured: pointing to stale minikube-vm.
To fix the kubectl context, run minikube update-context

Despite kubectl working fine to connect to the minikube cluster:

$ kubectl get all
NAME                 TYPE        CLUSTER-IP   EXTERNAL-IP   PORT(S)   AGE
service/kubernetes   ClusterIP   10.96.0.1    <none>        443/TCP   1d

Furthermore, following the advice to run minikube update-context actually seems to break kubectl's ability to establish a connection:

$ minikube update-context
Reconfigured kubeconfig IP, now pointing at 142.93.30.44
$ kubectl get all
Unable to connect to the server: x509: certificate is valid for 178.128.176.122, 10.96.0.1, 10.0.0.1, not 142.93.30.44

/reopen
/remove-lifecycle rotten

gabrielgrant on 12 Oct 2018

👍2

All 7 comments

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

Prevent issues from auto-closing with an /lifecycle frozen comment.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or @fejta.
/lifecycle stale

fejta-bot on 7 Jan 2018

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten
/remove-lifecycle stale

fejta-bot on 10 Feb 2018

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

fejta-bot on 12 Mar 2018

this seems to still be the case in v0.30.0 -- the status command reports that kubectl is misconfigured:

$ minikube status
minikube: Running
cluster: Running
kubectl: Misconfigured: pointing to stale minikube-vm.
To fix the kubectl context, run minikube update-context

Despite kubectl working fine to connect to the minikube cluster:

$ kubectl get all
NAME                 TYPE        CLUSTER-IP   EXTERNAL-IP   PORT(S)   AGE
service/kubernetes   ClusterIP   10.96.0.1    <none>        443/TCP   1d

Furthermore, following the advice to run minikube update-context actually seems to break kubectl's ability to establish a connection:

$ minikube update-context
Reconfigured kubeconfig IP, now pointing at 142.93.30.44
$ kubectl get all
Unable to connect to the server: x509: certificate is valid for 178.128.176.122, 10.96.0.1, 10.0.0.1, not 142.93.30.44

/reopen
/remove-lifecycle rotten

gabrielgrant on 12 Oct 2018

👍2

/reopen

gabrielgrant on 12 Oct 2018

@gabrielgrant: You can't reopen an issue/PR unless you authored it or you are a collaborator.

In response to this:

/reopen

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.