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

Context with no permission to enumerate other namespaces will not enumerate pods #90

Open
AnsonT opened this issue Aug 5, 2021 · 4 comments
Labels
bug Something isn't working

Comments

@AnsonT
Copy link

AnsonT commented Aug 5, 2021

Describe the bug
If the user of the active context does not have permission to enumerate other namespaces, etc., errors will be shown and no pods are listed in the current namespace even though it's permitted for the user

To Reproduce
Steps to reproduce the behavior or a screencast

  • select a context with permission restrictions

Expected behavior

  • resources that the user have permission to view will be shown
  • resources that the user does not have permission to view will not be shown (perhaps a 'no permission' message be presented)

Desktop (please complete the following information):
MacOS 11.5
iTerm2 3.4.8
Bash 5.1.8
Kubectl Client Version 1.21.0
Kubectl Server Version 1.19
KDash version 0.2.3
Installed from homebrew

@deepu105
Copy link
Contributor

deepu105 commented Aug 5, 2021

Thaks for the report. I think I need to check permission and fail gracefully in this case

@mennthor
Copy link

This would be a nice fix.
In my case, I have the namespace I have permission for in my kubeconfig contexts definition.
Would it be sufficient for kdash to simply check that and if it's defined, just use that namespace and skip the get namespace cmd?

@deepu105 deepu105 added the bug Something isn't working label Jul 5, 2023
@andrej-badinka
Copy link

Would be great to fix this, now if the user has no right to list all namespaces, we cannot use kdash to access pods.

Would be helpful if kdash could only load the namespace that is set in the kube config, in case the user cannot access all namespaces.

@deepu105
Copy link
Contributor

deepu105 commented Oct 30, 2024 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

4 participants