Skip to content
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

Closed
rmgpinto opened this issue Jul 5, 2019 · 12 comments · Fixed by #4051
Closed

Skip login not working #4023

rmgpinto opened this issue Jul 5, 2019 · 12 comments · Fixed by #4051
Assignees
Labels
kind/bug Categorizes issue or PR as related to a bug. priority/critical-urgent Highest priority. Must be actively worked on as someone's top priority right now.

Comments

@rmgpinto
Copy link

rmgpinto commented Jul 5, 2019

Environment
Installation method: Amazon EKS
Kubernetes version: 1.13
Dashboard version: kubernetesui/dashboard:v2.0.0-beta1
Operating system: Amazon EKS
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 to https://<URL>/api/v1/login/status and gets a 200 OK.

Expected result

Skip login and redirect to kubernetes dashboard

@rmgpinto rmgpinto added the kind/bug Categorizes issue or PR as related to a bug. label Jul 5, 2019
@floreks floreks added the priority/critical-urgent Highest priority. Must be actively worked on as someone's top priority right now. label Jul 5, 2019
@floreks floreks self-assigned this Jul 5, 2019
@floreks
Copy link
Member

floreks commented Jul 5, 2019

Will take a look.

@dacodas
Copy link

dacodas commented Jul 7, 2019

I am also experiencing this.

@ghost
Copy link

ghost commented Jul 7, 2019

I've experienced this as well...

@Rick-Jongbloed
Copy link

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.

@floreks
Copy link
Member

floreks commented Jul 8, 2019

Generating admin token is also super easy and does not require skip option.

@ghost
Copy link

ghost commented Jul 8, 2019

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).

@ghost
Copy link

ghost commented Jul 8, 2019

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.

What do you mean? Oh I see now... https://github.com/kubernetes/dashboard/blob/master/aio/deploy/alternative.yaml

@ghost
Copy link

ghost commented Aug 23, 2019

Hi,
Hate to be a naysayer but the deployment
https://github.com/kubernetes/dashboard/blob/master/aio/deploy/alternative.yaml
removes the login but also means that the service account it uses (kubernetes-dashboard?) doesn't have permission to see anything :(

@floreks
Copy link
Member

floreks commented Aug 23, 2019

@whillas As expected. It is described in the docs how alternative deployment works and how it should be used.

@sguidos
Copy link

sguidos commented Jul 15, 2020

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.

@floreks
Copy link
Member

floreks commented Jul 15, 2020

Adding --enable-skip-login by default does not make much sense as SA used by dashboard has almost 0 privileges. If you want to alter default configurations I'd suggest to use the helm chart. We have recently added support for it.

@sguidos
Copy link

sguidos commented Jul 15, 2020

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 --disable-settings-authorizer option to give me what I want, a developer-friendly local Dashboard that lets me administer my local development Kubernetes.

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Categorizes issue or PR as related to a bug. priority/critical-urgent Highest priority. Must be actively worked on as someone's top priority right now.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants