Unable to access pod logs following redeployment while Lens is running

[andrei-dascalu]

Describe the bug
Following the latest updated I've done to version Lens: 2025.1.161916-latest on MacOS I have an issue that happens as follows:

• given a running pod with multiple containers
• click on said pod
• hover over one of the involved containers and select it
• a logs tab opens with an error saying Failed to load pods for tab: Pod "db4efaa7-420c-4137-813a-f896d91d1e68" does not exist in namespace "<my namespace>".

This happens following a deployment of a new container tag affecting the deployment controlling the pod, done since Lens was opened. If I reopen Lens with the same running pod, I can access logs as expected.
On the same pod, this behaviour does not happen with other options. For example, in the exact same conditions I can access any shell for any container in said pod, even as selecting logs for any container results in the above error (the UUID differs).

Using kubectl I can see logs normally.

To Reproduce
Steps to reproduce the behavior:

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

Expected behavior
be able to access logs

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

Environment (please complete the following information):

• Lens Version: 2025.1.161916-latest
• OS: Mac OS 15.2 Apple Silicon
• Installation method (e.g. snap or AppImage in Linux): downloaded dmg

[koshevka]

Hello @andrei-dascalu, thank you so much for reporting this bug and bringing it to our attention!

I’ve already addressed this issue with the appropriate team, and they will look into it as soon as possible. We’ll keep you updated on any progress.

Thanks again for helping us improve!

[loxy]

Also in Windows with just one container in a Pod