Deployment/StatefulSet/DaemonSet/CronJob details now show a pod + container picker with the pod's recent log tail (500 lines, no follow), sitting alongside the existing raw-manifest view. Pod resolution reuses buildGraph's ownerReferences-walking logic (ownerWorkloadID) so it stays consistent with the schedules-on edges already shown on the graph. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
cluster-map
Interactive topology view of the Project Chimera Deckhouse cluster -- namespaces group workloads (Deployment/StatefulSet/DaemonSet/CronJob), connected to Services (by label-selector match) and Ingresses (by backend reference), plus a physical-node layer showing what's actually scheduled where. Click any node for its live manifest.
Go backend (client-go, builds the graph fresh from the k8s API on every
/api/graph request -- no caching, no watch loop, correct by construction)
- a single-page Cytoscape.js frontend, no build step.
Phase 1 (current): plain in-cluster app, deployed like everything else in
this project (03-kubernetes/apps/cluster-map/ in the project-chimera
docs repo, mirrored to k8s-manifests for Argo). No Hubble traffic overlay
yet, no packaging as an actual Deckhouse module (ModuleConfig/ModuleSource)
-- both are deliberately deferred until the base idea proves useful.
See STATUS.md / OpenProject (chimera-core) in project-chimera for the
full design rationale and decision history.