This would make it easier to authenticate when accessing through a browser, e.g. accessing Dashboard.
Good idea. I wonder if we should dynamically generate the password, or if it's fine to just use a static documented one for all users.
Could you explain a little more what you need these creds for? I'm able to access the dashboard without authenticating (using kubectl proxy or the HostPort)
I don't have access to my Minikube at the moment, but if I recall these were the steps that prompted me to recreate this issue:
master-ip/uiUnauthorizedLooking at the config for my Minikube cluster and other clusters I had, it seemed the only difference was the lack of Basic Auth credentials being created and the browser asking for them.
I think we need to generate the password dynamically, otherwise we'd still be vulnerable to a CSRF.
FWIW, I've upgraded to Minikube 0.4 and this is no longer an issue for me.
Nice! I can confirm this works for me too. I'm not sure what changed, maybe the dashboard upgrade we did?
I think I'll close this for now.
What exactly are you trying to view? If you go to master-ip/ui it should
work.
On Wed, Jul 6, 2016 at 1:25 PM phil swenson [email protected]
wrote:
so what is the solution? I just installed minikube today( minikube
version: v0.5.0 on OS X ) and get the unauthorized message in the browser—
You are receiving this because you modified the open/close state.Reply to this email directly, view it on GitHub
https://github.com/kubernetes/minikube/issues/87#issuecomment-230895389,
or mute the thread
https://github.com/notifications/unsubscribe/ABopNlhIkJ6KPBTqNPmrT9TnwHw9dLsmks5qTA8_gaJpZM4IgmUQ
.
FWIW, I still saw this unauthorized response under minikube 0.6.0 when visiting either of the following:
https://$vm_ip:8443/ui
https://$vm_ip:8443/api/v1/proxy/namespaces/kube-system/services/kubernetes-dashboard
The latter was retrieved from kubectl cluster-info.
EDIT: Extra details:
OSX 10.11.5, MacBook Pro (Retina, 15-inch, Mid 2015), 16GB
VMWare Fusion, Professional Version 8.1.1 (3771013)
$ minikube start --disk-size=40g --cpus=8 --memory=8192 --vm-driver=vmwarefusion
$ minikube version
minikube version: v0.6.0
$ shasum -a 256 $(which minikube)
b901806e821598471e3493c787b88ee666ffa08d032053ec80954be9048e4ef2 /usr/local/bin/minikube
I am using kubernetes v1.3.5 and minikube v0.7.1.
kubectl cluster-info gives me:
Kubernetes master is running at https://192.168.99.100:8443
kubernetes-dashboard is running at https://192.168.99.100:8443/api/v1/proxy/namespaces/kube-system/services/kubernetes-dashboard
None of the above URLs work for me when I enter them in chrome browser. The browser complains about insecure connection. However, if I do "minikube dashboard", it opens up the dashboard page successfully at 192.168.99.100:30000. What are the above URLs supposed to show? Same as 192.168.99.100:30000?
in my dump i am seeing the following. That info section is like that for my entire buffer repeating every minute.
INFO: == Reconciling with addon-manager label ==
INFO: == Kubernetes addon reconcile completed at 2017-06-15T07:07:01+0000 ==
INFO: == Kubernetes addon ensure completed at 2017-06-15T07:08:00+0000 ==
INFO: == Reconciling with deprecated label ==
error: no objects passed to apply
INFO: == Reconciling with addon-manager label ==
INFO: == Kubernetes addon reconcile completed at 2017-06-15T07:08:01+0000 ==
INFO: == Kubernetes addon ensure completed at 2017-06-15T07:09:00+0000 ==
INFO: == Reconciling with deprecated label ==
error: no objects passed to apply
INFO: == Reconciling with addon-manager label ==
INFO: == Kubernetes addon reconcile completed at 2017-06-15T07:09:00+0000 ==
==== END logs for kube-system/kube-addon-manager-minikube ====
==== START logs for kube-system/kube-dns-196007617-4pxg0 ====
Error from server (BadRequest): the server rejected our request for an unknown reason (get pods kube-dns-196007617-4pxg0)
Most helpful comment
I am using kubernetes v1.3.5 and minikube v0.7.1.
kubectl cluster-info gives me:
Kubernetes master is running at https://192.168.99.100:8443
kubernetes-dashboard is running at https://192.168.99.100:8443/api/v1/proxy/namespaces/kube-system/services/kubernetes-dashboard
None of the above URLs work for me when I enter them in chrome browser. The browser complains about insecure connection. However, if I do "minikube dashboard", it opens up the dashboard page successfully at 192.168.99.100:30000. What are the above URLs supposed to show? Same as 192.168.99.100:30000?