Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

auth for https services

See original GitHub issue

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

We appreciate your feedback. Thank you for using microk8s.

after installing 1.14/stable the following holds:

[inspection-report-20190326_111105.tar.gz](https://github.com/ubuntu/microk8s/files/3009574/inspection-report-20190326_111105.tar.gz)


~$ 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
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

(note the https;// ). Available documentation shows http:// and appears not to mention what credentials to use. In /var/snap/microk8s/484/credentials there are some hints, e.g. perhaps user admin, pw admin, but

https://127.0.0.1:16443/api/v1/namespaces/kube-system/services/monitoring-grafana/proxy

trying that and other combinations from basic_auth.csv in the same directory keeps yielding

kind | "Status"
-- | --
apiVersion | "v1"
metadata | {}
status | "Failure"
message | "Unauthorized"
reason | "Unauthorized"
code | 401

Issue Analytics

State:
Created 4 years ago
Comments:5 (1 by maintainers)

Top GitHub Comments

5reactions

mrmowglicommented, Apr 13, 2019

The tutorial at https://tutorials.ubuntu.com/tutorial/install-a-local-kubernetes-with-microk8s#4 needs to include this information, otherwise there is no way to access the pages.

5reactions

kobaltzcommented, Mar 26, 2019

The username is admin and the password can be found with microk8s.config. At the very bottom, you should see password: XXXXX

Top Results From Across the Web

HTTP authentication - MDN Web Docs - Mozilla

The "Basic" HTTP authentication scheme is defined in RFC 7617, which transmits credentials as user ID/password pairs, encoded using base64.

Using OAuth 2.0 for Server to Server Applications | Authorization

Creating a service account · Open the Service accounts page. · If prompted, select a project, or create a new one. · Click...

Authenticating service-to-service | Cloud Run Documentation

For an end-to-end walkthrough of an application using this service-to-service authentication technique, follow the securing Cloud Run services tutorial.

Using Authentication With Web Service Security - IBM

Authorization uses information about a client's identity and/or roles to determine the resources or tasks that a client can perform. Credentials.

Understanding Authentication, Authorization, and Encryption

Authentication by a client usually involves the server giving a certificate to the client in which a trusted third party such as Verisign...