Hello. I'm Codedemans who loves Codex!
I wanted to see Kubernetes resource relationships at a glance in Lens, so I created an extension called LensFlow.
-- Example Screen --
When using Lens, I could see the detailed information of each resource well, but when following the actual service flow, I often had to navigate between multiple screens. To see which Service an Ingress connects to, what Deployments or Pods are behind that Service, and which ConfigMap, Secret, or PVC a workload references, more clicks were required than expected.
Especially when checking for failures or understanding a namespace for the first time, I wanted to quickly see "where this request actually leads" and "what resources are actually attached behind this Service", but with just the existing screen, drawing the entire structure in my head felt a bit cumbersome.
So Lens Flow focuses on showing workload relationships within a namespace as a single graph. It displays not only Ingress, Service, Deployment, ReplicaSet, and Pod, but also reference resources like ConfigMap, Secret, and PVC together, so you can see service flows and dependencies on a single screen.
The graph supports both horizontal and vertical directions, and you can filter to show only the resources you want to see. Clicking on each resource card takes you to Lens's default detail pane, so you can first check the overall structure and then view only the resources you need in detail.
It works as a Lens extension without requiring a separate sidecar or additional CLI installation.
While it's difficult to say it perfectly represents all Kubernetes configurations, it should be quite useful for quickly grasping typical workload flows or getting an overview of namespace structure for the first time.
Please try it out and if you find any inconveniences or have improvement ideas, I would appreciate it if you could leave feedback.
