Failed to load logs of pod

Lens Support & Troubleshooting
#1

Sometimes i cannot get to load logs of pod. It returns that error. But the pod exists

image
image1336Ă—166 27.9 KB

#2

Dear @realhuseyn

Thank you for reaching out to Lens Support!

Thanks for reporting a bug.

We are working on your issue. Stand by for further updates.

Regards,

Oleksandr from Lens

1 Like
#3

Dear @realhuseyn could you please provide more information? It might help us with this issue.

Regards,
Oleksandr from Lens Support

#4

I want to show the logs of a pod. Sometimes, I cannot show the logs and get the error in the attached screenshot.

#5

Hello @realhuseyn,

Could you try to set “All namespaces” at the top of the Pod tab?

We are waiting for you to reply.

Best Regards,
Tikhon Kudinov
Lens Support Engineer
Mirantis, Inc

#6

Hello. I have already set “All namespaces”, I am not in the specified namespace

#7

Hello @realhuseyn,

Is it possible to load logs outside of Lens? Through the kubectl?

We are waiting for you to reply.

Best Regards,
Tikhon Kudinov
Lens Support Engineer
Mirantis, Inc

#8

Hi @tkudinov, i’ve the same described problem like @realhuseyn .
I’m using following version:

Lens: 2025.10.230725-latest
Electron: 38.2.2
Chrome: 140.0.7339.133
Node: 22.19.0
on a Mac M1

I have this error since a few weeks, maybe 2 months ? Sometimes if a new pod is created while lens is already running, i click on “log” of the pod and the message appears:

Failed to load pods for tab: Pod “my-app-67d7d67f77-8qchm” does not exist in namespace “mynamespace”

To resolve this i have to disconnect from the cluster, reconnect again and there the log appears directly, without doing anything else.

It seems, that the list of pods in namespace is cached and not updated, when a new pod is created WHILE Lens is running.
This never happens to existing pods when lens ist started.

Please have a look, it’s really annoying.

Regards,
Kai

#9

Hi @kneuhaus.cc,

Thanks a lot for taking the time to share the details — and sorry for the inconvenience this issue has been causing. We’re aware of it, and it’s already being addressed in the current sprint. A fix will be included soon.

We really appreciate your patience and understanding!

2 Likes