How to login into microk8s dashboard?

General Discussions microk8s
1

Hi all,

I’ve installed microk8s on a Kubuntu 18.04 KVM virtual machine.

Snap says:

sysop@hoseplavm:/snap/microk8s/522$ sudo snap list
[sudo] password di sysop: 
Name      Version  Rev    Tracking  Publisher   Notes
core      16-2.39  6964   stable    canonical✓  core
lxd       3.13     10756  stable    canonical✓  -
microk8s  v1.14.1  522    stable    canonical✓  classic
sysop@hoseplavm:/snap/microk8s/522$

The cluster info says:

sysop@hoseplavm:/snap/microk8s/522$ kubectl get all --all-namespaces
NAMESPACE     NAME                                                  READY   STATUS    RESTARTS   AGE
kube-system   pod/heapster-v1.5.2-6b5d7b57f9-ltd2b                  4/4     Running   4          27h
kube-system   pod/kube-dns-6bfbdd666c-zwpj6                         3/3     Running   3          27h
kube-system   pod/kubernetes-dashboard-6fd7f9c494-z4zsj             1/1     Running   1          27h
kube-system   pod/monitoring-influxdb-grafana-v4-78777c64c8-5dsbw   2/2     Running   2          27h

NAMESPACE     NAME                           TYPE        CLUSTER-IP       EXTERNAL-IP   PORT(S)             AGE
default       service/kubernetes             ClusterIP   10.152.183.1     <none>        443/TCP             28h
kube-system   service/heapster               ClusterIP   10.152.183.167   <none>        80/TCP              27h
kube-system   service/kube-dns               ClusterIP   10.152.183.10    <none>        53/UDP,53/TCP       27h
kube-system   service/kubernetes-dashboard   ClusterIP   10.152.183.75    <none>        443/TCP             27h
kube-system   service/monitoring-grafana     ClusterIP   10.152.183.86    <none>        80/TCP              27h
kube-system   service/monitoring-influxdb    ClusterIP   10.152.183.73    <none>        8083/TCP,8086/TCP   27h

NAMESPACE     NAME                                             READY   UP-TO-DATE   AVAILABLE   AGE
kube-system   deployment.apps/heapster-v1.5.2                  1/1     1            1           27h
kube-system   deployment.apps/kube-dns                         1/1     1            1           27h
kube-system   deployment.apps/kubernetes-dashboard             1/1     1            1           27h
kube-system   deployment.apps/monitoring-influxdb-grafana-v4   1/1     1            1           27h

NAMESPACE     NAME                                                        DESIRED   CURRENT   READY   AGE
kube-system   replicaset.apps/heapster-v1.5.2-5c5498f57c                  0         0         0       27h
kube-system   replicaset.apps/heapster-v1.5.2-6b5d7b57f9                  1         1         1       27h
kube-system   replicaset.apps/heapster-v1.5.2-89b48dff                    0         0         0       27h
kube-system   replicaset.apps/kube-dns-6bfbdd666c                         1         1         1       27h
kube-system   replicaset.apps/kubernetes-dashboard-6fd7f9c494             1         1         1       27h
kube-system   replicaset.apps/monitoring-influxdb-grafana-v4-78777c64c8   1         1         1       27h
sysop@hoseplavm:/snap/microk8s/522$

I’m able to access the dashboard; but to authenticate I have to select or kubeconfig or token.

Neither work.

For kubeconfig I selected the file

sysop@hoseplavm:/snap/microk8s/522$ sudo cat /var/snap/microk8s/current/credentials/client.config 
[sudo] password di sysop: 
apiVersion: v1
clusters:
- cluster:
    certificate-authority-data: LS0tLS1CRUdJTiBDRVJUSUZJQ0FURS0tLS0tCk1JSURDVENDQWZHZ0F3SUJBZ0lVVHhyVDJYdWt3SHVOd1Z5WE40N0g3dU85VFk0d0RRWUpLb1pJaHZjTkFRRUwKQlFBd0ZERVNNQkFHQTFVRUF3d0pNVEkzTGpBdU1DNHhNQjRYRFRFNU1EWXdOREV4TURFd01Wb1hEVFEyTVRBeQpNREV4TURFd01Wb3dGREVTTUJBR0ExVUVBd3dKTVRJM0xqQXVNQzR4TUlJQklqQU5CZ2txaGtpRzl3MEJBUUVGCkFBT0NBUThBTUlJQkNnS0NBUUVBeG96d2VCcXdCdmF6OWhxSEcxZGhuNjk2TDVjU0xIdUtqSGpZTmdFMlVzZXgKMG1VaTYwWThEZnVEYStXaWpSN1ZHWVZFYkNqRmVnRU5LQzBrcW9oRnVLRk9jTmlJaUcxOXlyaGxJWTZ6SnRKNQpUT04yQ0RiRTkvZEt6YnhBSklIQWNvQ0JzZU1RWk5kSzhXclZWZlJGWlFIOUh6Z1EzSGFjUHZvblBOZElrZ0NvCmtscXhkWVVuSmpMVlc1ZGZFelA0Y21PTmNKRGtkWHVqcUhkZ254RmV3T3BUTmQzZm5BTDFBdXJweXByMFMrOTAKdTlRYWhHREdWT3lGeW83eU9zVGU5RG9USDc1UStPeGlNTWhZUHcySmRGT2tQRklqalJRRXlET0F2cXE4N3BhMAo3M3JNRjVqaGkyUTRTcWtmME90TUh0cDBCVXVoUTJLbjdTUzJSanlQVlFJREFRQUJvMU13VVRBZEJnTlZIUTRFCkZnUVVNTnlYV0pycFF3TDJ4cllkaTdleExRbm1rWk13SHdZRFZSMGpCQmd3Rm9BVU1OeVhXSnJwUXdMMnhyWWQKaTdleExRbm1rWk13RHdZRFZSMFRBUUgvQkFVd0F3RUIvekFOQmdrcWhraUc5dzBCQVFzRkFBT0NBUUVBWHBlRgoxb2ZpVVhNMDZicDhmWURxNDlpQVZTaFR2K0NUOENQUVcxcXE3Y2M2NzBTRERETGQyVXdDWFk0cCtYa1hiZVVICnUveFVUeFJlczB6dDFDQ1RUMzFHaE14VzduVWR3UGF2U0NMbitvSGRtbFlOc0xzTnZ3aHBhRWxKNUNDT0FkZXYKWFVmb3NKU3pHdDQ3R2VLV3krY1pGWW9FUVM2VVNyUCtjV1E0ckdLSnJ3NkFYQ3UrelFBWGRVKzNxRm8rUFFHaQphRVRsbXIvZTV3YlF0VlNiNGJKc012K2RTUzBEdVNJVnZTN3BkTmlsS3BuOGIzOHpoQzJRTzVSd0pjSjhaKzQ3ClBMOGs1dzN5Z3BEQjlyblZOY1lieUtFMHVUNHpnZ0tvSHVkdEdkMHkwWnZySjFTYzczMDVUWVRBR1lJd3d0Q2YKbVRjNVNNeXlkbklSTld4ZEpnPT0KLS0tLS1FTkQgQ0VSVElGSUNBVEUtLS0tLQo=
    server: https://127.0.0.1:16443
name: microk8s-cluster
contexts:
- context:
    cluster: microk8s-cluster
    user: admin
name: microk8s
current-context: microk8s
kind: Config
preferences: {}
users:
- name: admin
user:
    username: admin
    password: YzRYZTlWbjN1TmFHR01kOUJWaGFndzhxejhsUWNldm1ia2FjcWRlYVBOOD0K

Trying this file as kube config file gives an “Authentication failed” error

Using the token method I took the token from

sysop@hoseplavm:/snap/microk8s/522$ sudo cat /var/snap/microk8s/current/credentials/basic_auth.csv 
YzRYZTlWbjN1TmFHR01kOUJWaGFndzhxejhsUWNldm1ia2FjcWRlYVBOOD0K,admin,admin,"system:masters"
sysop@hoseplavm:/snap/microk8s/522$

But also this gave the “Authentication failed error”

What can I do to anthenticate?

2

Hi @Mirto we have a PR up to update that dashboard. For now you can either click on “skip” or use the token found with:

microk8s.kubectl -n kube-system get secret
microk8s.kubectl -n kube-system describe secret default-token-{xxxxxx}

as described in https://github.com/ubuntu/microk8s/issues/292#issuecomment-474866818

2 Likes
3

Thanks. It worked!