v1.0.9

What's new

k8s-blast-radius — the view now actually renders ring 2.

Previously the tool description promised a two-ring radial (ring 1 = affected deployments, ring 2 = downstream user-facing services), but the view only drew ring 1. The APM-enriched data was returned in the payload and never visualized.

Now, when APM telemetry is present, ring 2 renders user-facing services grouped by namespace:

• Services cluster on the arc nearest their namespace's affected deployments (circular-mean positioning to avoid 0/2π wraparound artifacts)
• Faint blue connectors tie ring 1 deployments to their namespace's service cluster
• Small blue nodes keep ring 1 (infrastructure layer) as the visually dominant layer
• Summary card adds "N downstream services — user-facing" row

When APM is absent, nothing ring-2-related renders and the existing downstream_services_note footer still explains the limitation.

Why it matters

Blast radius differentiates from kubectl by answering "will customers feel this?" — not just "what pods are on this node?". Ring 2 closes the gap between infrastructure impact and user impact in one glance.

Install

• Claude Desktop: download example-mcp-app-observability.mcpb and double-click
• Skills: upload each *.zip in Claude Desktop → Customize → Skills