kro: embed resource graphs on detail pages (0.2.0-alpha)

[danbruno101]

What this adds

Embedded resource graphs on the kro plugin's detail pages, and a 0.2.0-alpha release for them.

• RGD detail gains a Template Graph: a synthetic RGD root, one node per spec.resources entry, and edges from the dependency graph kro publishes in status.resources[].dependencies (never re-derived from CEL). External externalRef resources and includeWhen conditionals are marked.
• Instance detail gains a Resource Graph of the objects kro actually created, with live health. It is fed by the sub-resource watch set the page already owns, so the graph and the existing Sub-resources table always render from the same data.

Renderer selection at runtime

kubernetes-sigs/headlamp#6992 exposes Headlamp's Map renderer to plugins as window.pluginLib.ResourceMap.GraphView. That export is newer than Headlamp 0.44.0, and a build-time import of lib/ResourceMap would fail to typecheck against the released @kinvolk/headlamp-plugin and break the plugin at load time on released hosts. So the component is looked up on window.pluginLib at render time:

• host has the export → sections render Headlamp's own GraphView, so nodes get KubeIcons and open the standard node details panel on click;
• older host → a small @xyflow/react renderer (FallbackGraphView). That library comes from headlamp-plugin's own dependency tree, so this adds no runtime dependency.

Detection fails closed: anything other than a renderable component falls back.

Scoping an embedded map

defaultSources is appended to (not substituted for) the globally registered map sources, so scoping comes from defaultNodeSelection — the native GraphView renders only the selected node's connected component. Two consequences shaped the code:

• the template graph is rooted at a synthetic node (template-root, deliberately not the RGD's uid, which the global source already uses with edges to every instance) so the DAG is always a single connected component;
• instance ownership edges reuse the global map source's kro-owns-<uid> ids, so first-wins dedupe collapses duplicates instead of drawing them twice.

Known behaviors inherited from the Map renderer

Documented in the plugin README and filed upstream as kubernetes-sigs/headlamp#7242 (requesting an opt-in embedded mode): the embedded view writes ?node=/?group= to the page URL, resets the global namespace filter on mount, and shows the full Map chrome.

Testing

• npm run lint, npm run tsc, npm run test (53 tests, 8 files), npm run build all pass.
• New unit tests cover the graph builders (single-connected-component guarantee, defensive edge filtering, Inactive-RGD safety, edge ids, layout layering and cycle guard), the runtime detection (absent / non-renderable / function / lazy-object shapes), and the GraphSource adapter.
• Verified live against a kind cluster running kro 0.9.2 with the kro-genaiops-demo RGDs, on both paths: the fallback renderer on Headlamp 0.44.x desktop, and the native GraphView on Headlamp built from main. Checked node-click details, live convergence after deleting the Deployment's pods, and that the global Map view and View-in-Map deep links still work.

Screenshots

Embedded template graph (RGD detail)	Embedded instance graph

Node details opened from a graph node

🤖 Generated with Claude Code

https://claude.ai/code/session_016zqV1YPx3JSFGVXqoCp76s