You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
In our k8s env, a normal user has no permission to read the default namespace. k9s quits in this case, without letting me choose a namespace I have access to.
Describe the solution you'd like
I would like to use k9s as a tool I can fire up to get an overview of everything I am allowed to see. To explore/switch namespaces on the fly.
Describe alternatives you've considered
Atm I am listing every namespace with kubectl get namespaces, copy the one I am interested in, and fire up k9s with that explicit namespace provided
Additional context
For every deployed application with its dependencies, we have the rule to use a single namespace. Normally I use a UI to select the namespace and then fireup k9s to really interact with it. I would like to skip the ui-lookup part
I thought supplying -A would fix my issue, but it quits with an error when one of the namespaces cannot be accessed
~ ❯ k9s -A ⎈ ni-prod-defra 10:54:05
Error: [list] access denied on resource "":"v1/pods"
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
In our k8s env, a normal user has no permission to read the default namespace. k9s quits in this case, without letting me choose a namespace I have access to.
Describe the solution you'd like
I would like to use k9s as a tool I can fire up to get an overview of everything I am allowed to see. To explore/switch namespaces on the fly.
Describe alternatives you've considered
Atm I am listing every namespace with
kubectl get namespaces
, copy the one I am interested in, and fire up k9s with that explicit namespace providedAdditional context
For every deployed application with its dependencies, we have the rule to use a single namespace. Normally I use a UI to select the namespace and then fireup k9s to really interact with it. I would like to skip the ui-lookup part
I thought supplying
-A
would fix my issue, but it quits with an error when one of the namespaces cannot be accessedThe text was updated successfully, but these errors were encountered: