Sebastian Florek
Sebastian Florek
And the response of this call is what you see in the log viewer?
Interesting. The parameters are missing. We have to find a way to reproduce this.
We were focused on more important topics lately, like security and logging in mechanism. This feature is rather low on our priority list for now. No ETA.
> @floreks Are we able to display some kind of dialog here? Probably. [This](https://github.com/kubernetes/dashboard/blob/master/src/app/frontend/common/auth/service.js#L68) code prevents you from logging in. @Theoooooo Exposing Dashboard publicly using `kubectl proxy --address` is usually...
@Theoooooo You have to expose (using `kubectl proxy`) and access Dashboard locally (`localhost` or `127.0.0.1` domain). We will add inform dialog that will explain why this is blocked when user...
https://github.com/kubernetes/dashboard/wiki/Getting-started You can build and deploy your own version of Dashboard. We do not support accessing Dashboard in a non-secure way (via login page).
I'd rather not do this as it is not secure. Traffic from other device to the device that exposes API using `kubectl proxy -address xxx` will be unencrypted and easy...
/lifecycle frozen
I am not sure why would it matter for the local dev environment. When running locally I simply grant Dashboard itself full privileges and disable HTTPS. Another option is to...
/lifecycle frozen