The cluster doesn't have to be healthy for kubectl

[afbjorklund]

We only want to match the kubectl version with it

Closes #10717

BEFORE

$ kubectl version --client --output=json
🤷  The control plane node must be running for this command
👉  To start a cluster, run: "minikube start"

AFTER

$ kubectl version --client --output=json
{
  "clientVersion": {
    "major": "1",
    "minor": "20",
    "gitVersion": "v1.20.2",
    "gitCommit": "faecb196815e248d3ecfb03c680a4507229c2a56",
    "gitTreeState": "clean",
    "buildDate": "2021-01-13T13:28:09Z",
    "goVersion": "go1.15.5",
    "compiler": "gc",
    "platform": "linux/amd64"
  }
}

[afbjorklund]

Still not fully fixed, since mustload will abort if there is no config:

$ kubectl version --client
* Profile "minikube" not found. Run "minikube profile list" to view all profiles.
  - To start a cluster, run: "minikube start

Maybe it should just have used constants.DefaultKubernetesVersion

[medyagh]

how about adding an integration test for this ? so on a NOT running minikube profile (maybe start with --dry-run) and then try kubectl on it ? similar to the kubectl subtest in functional test?

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: afbjorklund

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [afbjorklund]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment