The Developer's View
Octant (originally built by VMware) took a fundamentally different approach to cluster visualization. Instead of listing resources in tables, it focused on visualizing the relationships between resources — answering the question "what is connected to what?" rather than "what exists?"
How it worked: Octant ran as a local binary on your machine (not inside the cluster) and connected to the Kubernetes API via your kubeconfig. Its signature feature was a Resource Graph: select any workload, and Octant would draw a node graph showing every Kubernetes object connected to it.
For example, selecting a Deployment would show:
- The Deployment node at the center
- Lines to its child ReplicaSet
- Lines from the ReplicaSet to each Pod
- Lines from each Pod to the Service that selects it
- Lines from each Pod to the ConfigMaps and Secrets it mounts
- Lines from each Pod to its ServiceAccount
This made it immediately obvious when a Pod was missing a required ConfigMap, or when a Service's label selector didn't match any Pods (a common misconfiguration).
Status Note: Octant was archived in 2023 and is no longer actively maintained. It should not be used for new setups. However, its core philosophy — that relationship visualization is as important as resource listing — has been validated and adopted by other tools:
- Lens includes a "Map" view that provides similar relationship graphs
- ArgoCD's UI shows application resource trees with parent-child relationships
- Headlamp (a newer open-source dashboard) includes relationship views
Understanding Octant's approach is valuable because it teaches you what to look for in any dashboarding tool: not just "can I see my Pods?" but "can I understand how my resources relate to each other?"