In Lens, we encountered an issue with creating and using a service account with pod viewer access. We created an RBAC role to allow our developers to view pod logs, then assigned this viewer role to a service account and used its token to connect to our local Kubernetes cluster. However, in the new version, users are unable to see any pods or select the default namespace in the UI. This issue did not occur in the previous version, where the same token worked as expected.
Hello @arrwind03,
thank you for your feedback! We’re already aware of this bug, and our developers are actively working on a fix.
Hi, the bug will be fixed in the next release. For a workaround please set the namespace to Accessible Namespaces in Cluster Settings.
Thank you for the response! I’m eagerly awaiting the fix. Additionally, we’ve encountered another issue: sometimes, when a date and time are selected in the new update, it doesn’t reflect in the logs. Instead, it always displays the current time logs.
Logs are tied to the lifecycle of the Pod. If a Pod is restarted or deleted, the previous logs are no longer available unless they were persistently stored. Can you please check if your Pod is even able to provide logs for your selected date? But yeah, Lens shouldn’t jump to current date. We’re working here to improve UX, e.g. disabling dates in the calendar or make them non-clickable when there are no logs available.
Thanks again for your feedback, we really appreciate!
Auto-Update Concern: I am using macOS, and I’ve noticed that my Lens application gets updated to the latest version automatically without any prompt. It would be helpful to have an option, such as a button to turn auto-updates off or a prompt asking for confirmation before updating. This would allow me to decide when to update and avoid unexpected disruptions.
Hi crothmann,
Thank you for your response. I have identified some additional points to share. Before diving into them, I’ll reiterate the message you posted earlier:
- Logs Issue: I noticed that logs from yesterday are visible when scrolling, but if I select a specific date and time using the calendar, it doesn’t load the logs for the selected period. Instead, it shows only the current time logs.
- Missing “All Pods” Option: In this update, the “All Pods” option is missing. I have two or more pods for certain services, and currently, I need to check logs for each pod individually. I would prefer to have a single log page where I can view logs for all pods, similar to the previous version.
- Cluster Navigation Issue: I am working with multiple clusters. When I select pods from one cluster and perform any action, then switch to pods from another cluster, the page gets replaced by the new cluster’s view. It would be better if each cluster’s pods could open in a new window or tab, allowing simultaneous views.
Thank you for looking into these issues!
" Missing “All Pods” Option :"
The next release will have a “Jump to Parent” button which is effectively same as “All Pods”. For a workaround you can manually navigate to the parent resource and then open logs for that resource.