Now that we have enabled the dns and dashboard addons we can access the available dashboard. To do so we first check the deployment progress of our addons with microk8s.kubectl get all --all-namespaces. It only takes a few minutes to get all pods in the “Running” state:
NAMESPACE NAME READY STATUS RESTARTS AGE
kube-system pod/coredns-f7867546d-zb9t5 1/1 Running 0 3m25s
kube-system pod/heapster-v1.5.2-844b564688-5bpzs 4/4 Running 0 64s
kube-system pod/kubernetes-dashboard-7d75c474bb-jcglw 1/1 Running 0 3m19s
kube-system pod/monitoring-influxdb-grafana-v4-6b6954958c-nc6bq 2/2 Running 0 3m19s
NAMESPACE NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE
default service/kubernetes ClusterIP 10.152.183.1 <none> 443/TCP 3m34s
kube-system service/heapster ClusterIP 10.152.183.7 <none> 80/TCP 3m19s
kube-system service/kube-dns ClusterIP 10.152.183.10 <none> 53/UDP,53/TCP,9153/TCP 3m25s
kube-system service/kubernetes-dashboard ClusterIP 10.152.183.64 <none> 443/TCP 3m19s
kube-system service/monitoring-grafana ClusterIP 10.152.183.3 <none> 80/TCP 3m19s
kube-system service/monitoring-influxdb ClusterIP 10.152.183.203 <none> 8083/TCP,8086/TCP 3m19s
NAMESPACE NAME READY UP-TO-DATE AVAILABLE AGE
kube-system deployment.apps/coredns 1/1 1 1 3m25s
kube-system deployment.apps/heapster-v1.5.2 1/1 1 1 3m19s
kube-system deployment.apps/kubernetes-dashboard 1/1 1 1 3m19s
kube-system deployment.apps/monitoring-influxdb-grafana-v4 1/1 1 1 3m19s
NAMESPACE NAME DESIRED CURRENT READY AGE
kube-system replicaset.apps/coredns-f7867546d 1 1 1 3m25s
kube-system replicaset.apps/heapster-v1.5.2-6b794f77c8 0 0 0 3m19s
kube-system replicaset.apps/heapster-v1.5.2-6f5d55456 0 0 0 84s
kube-system replicaset.apps/heapster-v1.5.2-844b564688 1 1 1 64s
kube-system replicaset.apps/kubernetes-dashboard-7d75c474bb 1 1 1 3m19s
kube-system replicaset.apps/monitoring-influxdb-grafana-v4-6b6954958c 1 1 1 3m19s
Kubernetes dashboard
As we see above the kubernetes-dashboard service in the kube-system namespace has a ClusterIP of 10.152.183.64 and listens on TCP port 443. The ClusterIP is randomly assigned, so if you follow these steps on your host, make sure you check the IP adress you got. Point your browser to https://10.152.183.64:443 and you will see the kubernetes dashboard UI. To access the dashboard use the default token retrieved with:
token=$(microk8s.kubectl -n kube-system get secret | grep default-token | cut -d " " -f1)
microk8s.kubectl -n kube-system describe secret $token
Grafana dashboard
Let’s use an alternative approach to access hosted services. The API server proxies our services, here is how to get to them:
> microk8s.kubectl cluster-info
Kubernetes master is running at https://127.0.0.1:16443
Heapster is running at https://127.0.0.1:16443/api/v1/namespaces/kube-system/services/heapster/proxy
CoreDNS is running at https://127.0.0.1:16443/api/v1/namespaces/kube-system/services/kube-dns:dns/proxy
Grafana is running at https://127.0.0.1:16443/api/v1/namespaces/kube-system/services/monitoring-grafana/proxy
InfluxDB is running at https://127.0.0.1:16443/api/v1/namespaces/kube-system/services/monitoring-influxdb:http/proxy
We need to point our browser to https://127.0.0.1:16443/api/v1/namespaces/kube-system/services/monitoring-grafana/proxy and use the username and password shown with microk8s.config.
