Power tools
Dependency Graph
Almost every resource detail view has a Graph tab showing how it connects to other resources in the cluster - upstream traffic sources, owners, dependents, and sidecar configuration.
What the graph shows
Pick any resource and the graph walks both directions:
- Upstream - what sends traffic here? (Gateways → HTTPRoutes / Ingresses → Services)
- Owners - what manages this? (Deployment → ReplicaSet → Pod)
- Downstream - what does this contain or schedule? (Pod → Node, ConfigMaps, Secrets, ServiceAccount)
- Cloud annotations - GKE-specific (BackendConfig, FrontendConfig, ManagedCertificate, GCPBackendPolicy, HealthCheckPolicy); AWS (IRSA via
eks.amazonaws.com/role-arn)
Layout
Two orientations, toggled in the top-right:
- Horizontal - flows left → right (Gateway on the left, Pod on the right)
- Vertical - flows top → bottom
Kubius picks a sensible default per resource type. Your last choice is remembered globally.
The focus resource is highlighted with a thicker dashed border. Layout uses a force-directed algorithm with sensible default columns per resource - it avoids overlap, keeps related nodes close, and stays stable as the underlying data updates.
Interaction
- Click a node - single-click opens the detail in the current panel; right-click opens in a new window or opens the resource
- Double-click a node - opens it in a new window
- Drag the canvas - pan
- ⌘ scroll or pinch - zoom in / out
- + / - in the toolbar - zoom buttons
- Focus button - recenters and resets zoom to 1×
- Double-click empty canvas - quick zoom in
Status colours
Node opacity reflects activity:
- Full opacity - running / ready / has traffic
- 35% opacity - stopped, scaled to zero, or no ready replicas
This lets you spot dead branches at a glance - a Deployment with five stale ReplicaSets shows the inactive ones faded out.
Export
The Export Image menu offers three formats:
- PNG (Transparent) - high-DPI raster
- PNG (White Background) - same but white-backed
- SVG (Vector) - true vector with proper text and curves
PNG export uses the same ImageRenderer flow as metric charts. SVG export emits <rect> for nodes and <path> for edges (cubic bezier for cross-column edges, straight lines for same-column connections).
What you’ll find in the graph for…
- Pod - owning ReplicaSet / Deployment / StatefulSet / DaemonSet / Job, scheduled Node, exposing Services, mounted ConfigMaps / Secrets / PVCs, ServiceAccount, IRSA (AWS) link
- Deployment - ReplicaSets, backing Pods, exposing Services, HPAs, PDBs, NetworkPolicies, upstream Ingresses / HTTPRoutes / Gateways, GCP backend policies, ConfigMaps / Secrets / PVCs / SA
- Service - upstream Ingresses / HTTPRoutes / Gateways, backing Pods, GKE cloud annotations (BackendConfig, ManagedCert, FrontendConfig, TargetGroupBinding for AWS)
- Node - every pod scheduled on it
- Gateway - attached HTTPRoutes → backend Services → Pods → Node
- PVC - mounting Pods → Node, bound PersistentVolume
- ServiceAccount - bound RoleBindings / ClusterRoleBindings → Roles / ClusterRoles, pods using the SA