Continue to function as far as possible in scenarios where the user lacks certain permission. For example, when the user has a specific Kubernetes namespace in mind, but lacks permission to get, list, or describe namespaces.
Why is this needed:
So that users are able to enjoy Lens in more business environments.
If you already know the name of the namespace that you have access to but cannot list namespaces then you can hardcode that namespace under cluster settings. The heading should be "Accessible Namespaces".
What would you like to be added:
Continue to function as far as possible in scenarios where the user lacks certain permission. For example, when the user has a specific Kubernetes namespace in mind, but lacks permission to get, list, or describe namespaces.
Why is this needed:
So that users are able to enjoy Lens in more business environments.
Environment you are Lens application on: