-
Notifications
You must be signed in to change notification settings - Fork 4.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Skip login not working #4023
Comments
Will take a look. |
I am also experiencing this. |
I've experienced this as well... |
for what it's worth, if you use the alternative yaml file, you don't need the skip button and you can use the dashboard. |
Generating admin token is also super easy and does not require skip option. |
This is definitely a luxury feature, mostly used where security is not a big regard and also where users don't want to generate an admin token (ex./ minikube). |
|
Hi, |
@whillas As expected. It is described in the docs how alternative deployment works and how it should be used. |
Manually cloning the repo and adding the --enable-skip-login argument to the alternative.yaml file within the container spec of the kubernetes-dashboard Deployment give me exactly what I, and I expect many others here, are looking for: a way to easily install a fully functional dashboard on our local development machines without any need to authenticate or login. Is there a way to pass the enable-skip-login args option to the installation command "kubectl create -f .../alternative.yaml" ? That would easily give us the desired result of getting a developer-friendly dashboard installation directly from the repository, thanks. |
Adding |
I have tried to use the Helm Chart, which has its own issues correctly using the extraArgs, see the issue I just opened, thanks. You are correct about 0 privileges with just --enable-skip-login. I forgot to include that I also use the Also, once I find out how to pass these options to the Hem Chart, it would be nice to have the alternative.yaml exposed as a separate Helm Chart installation. |
Environment
Steps to reproduce
I've added
--enable-skip-login, --disable-settings-authorizer
to the default dashboard yaml files.Observed result
When clicking the
Skip
button, the page only sends a request tohttps://<URL>/api/v1/login/status
and gets a200 OK
.Expected result
Skip login and redirect to kubernetes dashboard
The text was updated successfully, but these errors were encountered: