Failed to open a pod shell

[cxyfreedom]

Describe the bug

failed to open a pod shell: Failed to prepare kubectl exec args: (Forbidden) nodes "some-node" is forbidden: User "some service account" cannot get resource "nodes" in API group "" at the cluster scope

Lens old version is normal. I don't know secretly changed in latest verison.

To Reproduce
Steps to reproduce the behavior:

1. Go to '...'
2. Click on '....'
3. Scroll down to '....'
4. See error

Expected behavior
A clear and concise description of what you expected to happen.

can open pod shell

Screenshots
If applicable, add screenshots to help explain your problem.

Environment (please complete the following information):

• Lens Version:
• OS: [e.g. OSX]
• Installation method (e.g. snap or AppImage in Linux):

Logs:
When you run the application executable from command line you will see some logging output. Please paste them here:

Your logs go here...

Kubeconfig:
Quite often the problems are caused by malformed kubeconfig which the application tries to load. Please share your kubeconfig, remember to remove any secret and sensitive information.

your kubeconfig here

Additional context
Add any other context about the problem here.

[koshevka]

Dear @cxyfreedom

Thank you for reaching out to Lens Support!
We will be sure to update our development team.

Warm regards,
Oleksandr from Lens Support

[panuhorsmalahti]

Thank you for your report. This is a known issue and will be fixed as part of the next release. The issue is caused by lack of permissions to retrieve the Node where the Pod resides.

[nickaein]

Thanks for the update! I wanted to clarify how the fix will be implemented in the next release. Will this permission requirement become optional, or will it be handled differently?

I ask because previous versions of Lens worked without requiring this Node permission, and we'd prefer to maintain that approach if possible. From a security standpoint, we're hesitant to grant this additional permission, especially since users can still successfully kubectl exec into pods without it.

[panuhorsmalahti]

Thanks for the update! I wanted to clarify how the fix will be implemented in the next release. Will this permission requirement become optional, or will it be handled differently?

I ask because previous versions of Lens worked without requiring this Node permission, and we'd prefer to maintain that approach if possible. From a security standpoint, we're hesitant to grant this additional permission, especially since users can still successfully kubectl exec into pods without it.

This permission will be optional. We added it so that we can support Pod Shell into Windows Nodes.

[min-min-min]

Me too. I encountered the same problem

[min-min-min]

Me too. I encountered the same problem

At present, I can't get in and there's no entry to download the old version either

[vyshnevska]

+1 to the issue. @panuhorsmalahti is there any target date when to expect the next release (the one with the fix)?