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

Users who have no permission on the default cluster cannot log in kubeapps #6917

Open
cwyj opened this issue Oct 9, 2023 · 5 comments
Open
Labels
awaiting-more-evidence Need more info to actually get it done. kind/bug An issue that reports a defect in an existing feature

Comments

@cwyj
Copy link

cwyj commented Oct 9, 2023

Describe the bug
I have a multiple clusters kubeapps,include cluster1 and cluster2.Cluster1 is the default cluster which Kubeapps itself installed. User may have cluster2 permission to deploy,but do not have cluster1 permission.When the user try to login kubeapps,due to have no permission for cluster1,the dashboard stop at Fetching Cluster Info...
image

This happened in the newer version v2.6.1.
Older version v2.0.0 no such case,User who has no default cluster permission can also login kubeapps and switch to another cluster with permissions.
Has this issue been fixed in a newer version?My k8s cluster version is 1.26.1

@cwyj cwyj added the kind/bug An issue that reports a defect in an existing feature label Oct 9, 2023
@cwyj
Copy link
Author

cwyj commented Oct 9, 2023

Describe the bug I have a multiple clusters kubeapps,include cluster1 and cluster2.Cluster1 is the default cluster which Kubeapps itself installed. User may have cluster2 permission to deploy,but do not have cluster1 permission.When the user try to login kubeapps,due to have no permission for cluster1,the dashboard stop at Fetching Cluster Info... image

This happened in the newer version v2.6.1. Older version v2.0.0 no such case,User who has no default cluster permission can also login kubeapps and switch to another cluster with permissions. Has this issue been fixed in a newer version?My k8s cluster version is 1.26.1

@absoludity I ask for your help again

@absoludity
Copy link
Contributor

Thanks @cwyj for the report. Sounds like a regression... the intent is what you describe for the previous version. If this is a new regression, it's unlikely to be fixed in the soon to be released new version, but we'll then investigate and fix it.

@cwyj
Copy link
Author

cwyj commented Oct 10, 2023

Thanks @cwyj for the report. Sounds like a regression... the intent is what you describe for the previous version. If this is a new regression, it's unlikely to be fixed in the soon to be released new version, but we'll then investigate and fix it.

Thank you very much.Looking forward to the new version after the fix.
As for now,I give view permission to all users for default cluster.So they can login successfully and switch to another clusters.

@antgamdia
Copy link
Contributor

👋 @cwyj, did v2.9.0 finally work for you?

@antgamdia antgamdia added the awaiting-more-evidence Need more info to actually get it done. label Jan 8, 2024
@antgamdia antgamdia added this to the Community requests milestone Jan 8, 2024
@cwyj
Copy link
Author

cwyj commented Jan 9, 2024

👋 @cwyj, did v2.9.0 finally work for you?

no, i haven't tried v2.9.0 yet.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
awaiting-more-evidence Need more info to actually get it done. kind/bug An issue that reports a defect in an existing feature
Projects
Status: 🗂 Backlog
Development

No branches or pull requests

3 participants