docs/dev/libvirt-howto: Masters lack the admin kubeconfig

[wking]

Or at least, it's in what looks like an unreliable location ;). Here's my local kubeconfig:

$ sha1sum wking/auth/kubeconfig
dd7f1796fe5aed9b0f453498e60bfea9c6a56586  wking/auth/kubeconfig

And here's looking on master:

[core@wking-master-0 ~]$ sudo find / -xdev -name 'kubeconfig*' -exec sha1sum {} \+ 2>/dev/null
aa7e5544c36f2b070c33cbbea12102d64bc52928  /sysroot/ostree/deploy/rhcos/var/lib/kubelet/kubeconfig
aa7e5544c36f2b070c33cbbea12102d64bc52928  /var/lib/kubelet/kubeconfig
227e8aa1c09c7b5f8602a5528077f3bd34b8544e  /etc/kubernetes/kubeconfig
dd7f1796fe5aed9b0f453498e60bfea9c6a56586  /etc/kubernetes/checkpoint-secrets/kube-system/pod-checkpointer-5crhb/controller-manager-kubeconfig/kubeconfig
[core@wking-master-0 ~]$ grep 'user: ' /etc/kubernetes/kubeconfig
    user: kubelet

Reaching into checkpoint-secrets is probably not what we want to recommend, so I'm suggesting folks just copy their kubeconfig over from their local host.

CC @alejovicu

[abhinavdahiya]

i want to drop this section of use the kubeconfig on nodes. Why do we need this?
There is kubeconfig on user's machine.
And tectonic-console and the openshift console both have a way to get a kubeconfig corresponding to the logged in user.

[wking]

i want to drop this section of use the kubeconfig on nodes...

The docs I'm adjusting here are originally from 04266e2 (#93). As @cgwalters mentions there, the "SSH and then run this" approach is useful when you cannot resolve masters over DNS (so the URI in the kubeconfig doesn't work from your host). But you can SSH in by IP and then use the kubeconfig (because libvirt has the DNS set up for you on the bootstrap and master nodes).

[abhinavdahiya]

can we ask users to always scp their local kubeconfig and use that. so that you scp it any node and run with it.

[wking]

can we ask users to always scp their local kubeconfig and use that. so that you scp it any node and run with

Done with 9efc2e0 -> 23ca6a1.

[abhinavdahiya]

/lgtm

[openshift-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: abhinavdahiya, wking

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 [abhinavdahiya,wking]

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