Microk8s: How to change dashboard / grafana login credentials?

Created on 27 Mar 2019  Â·  5Comments  Â·  Source: ubuntu/microk8s

Please run microk8s.inspect and attach the generated tarball to this issue.

We appreciate your feedback. Thank you for using microk8s.
https://127.0.0.1:16443/api/v1/namespaces/kube-system/services/monitoring-grafana/proxy

It prompts for username/password....

Most helpful comment

Hi, I did the following to get microk8s running (using this guide):

root@my-pc~# sudo snap install microk8s --classic
root@my-pc~# microk8s.enable dns dashboard

root@my-pc:/home/myuser/Downloads/microservices-demo# 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
KubeDNS 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

Problem is I cant access the Grafana Board at https://127.0.0.1:16443/api/v1/namespaces/kube-system/services/monitoring-grafana/proxy , because i don't know where to look up the username/password that is generated by default.

EDIT:

OK I found the default username/password in the file: /var/snap/microk8s/current/credentials/basic_auth.csv

All 5 comments

Got it!

How to change the long crypted password to a customized one?

Right now this username/password are random strings created at MicroK8s install time. You should be able to add more uses in /var/snap/microk8s/current/credentials/basic_auth.csv. You can read more here: https://kubernetes.io/docs/reference/access-authn-authz/authentication/#static-password-file

Hi, I did the following to get microk8s running (using this guide):

root@my-pc~# sudo snap install microk8s --classic
root@my-pc~# microk8s.enable dns dashboard

root@my-pc:/home/myuser/Downloads/microservices-demo# 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
KubeDNS 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

Problem is I cant access the Grafana Board at https://127.0.0.1:16443/api/v1/namespaces/kube-system/services/monitoring-grafana/proxy , because i don't know where to look up the username/password that is generated by default.

EDIT:

OK I found the default username/password in the file: /var/snap/microk8s/current/credentials/basic_auth.csv

/var/snap/microk8s/current/config

On Thu, Apr 4, 2019, 17:37 keltik85 notifications@github.com wrote:

Hi, I did the following to get microk8s running (using this guide
https://tutorials.ubuntu.com/tutorial/install-a-local-kubernetes-with-microk8s#3
):

root@my-pc~# sudo snap install microk8s --classic
root@my-pc~# microk8s.enable dns dashboard

root@my-pc:/home/atekin/Downloads/microservices-demo# 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
KubeDNS 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

Problem is I cant access the Grafana Board at
https://127.0.0.1:16443/api/v1/namespaces/kube-system/services/monitoring-grafana/proxy
, because i don't know where to look up the username/password that is
generated by default.

—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/ubuntu/microk8s/issues/389#issuecomment-479825850,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ADsS-2fHd8srPyCS0Vk4qAq8aGHSO7Scks5vdcfcgaJpZM4cNLnP
.

Was this page helpful?
0 / 5 - 0 ratings