-
Notifications
You must be signed in to change notification settings - Fork 4.2k
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
Fail to login - Access Control is not helping #2558
Comments
As per documentation says:
By default
We deliberately do not provide exact steps of how to "generate" token as there are many ways of getting one. It is important that user reads Kubernetes documentation first and understands how different authentication and authorization mechanisms work in order to be able to use them. Dashboard tries to mimic behavior of You should start by reading: Creating and using service accounts is the easiest way of getting tokens, but not the only one. There are more ways described in Kubernetes documentation. We also do not want to copy & paste information that can be found in Kubernetes documentation, but rather point user to it by providing necessary links in our documentation. |
I do understand your point, but when trying to setup a kubernetes cluster for the first time, I may not want to know in depth how everything is working. Also, the authentication system seam to be very sophisticated. And before trying to learn how the authentication is working, I want to get into the dashboard. |
If you just want to access Dashboard with all privileges you can always try: https://github.com/kubernetes/dashboard/wiki/Access-control#admin-privileges After applying this you can use |
I think everything is clear here. Closing. |
I've created a new kubernetes cluster and added the dashboard. I have some trouble to log into the dashboard. Seam I'm not the only one. See #2524, #2474, #2476 and probably more.
Plz don't refer me to the access control page (https://github.com/kubernetes/dashboard/wiki/Access-control) I've already read it.
Is it possible to provide more explicit information about how to make the login work ?
e.g.:
Thanks,
The text was updated successfully, but these errors were encountered: