Idea: Cascade delete preview

[nadaverell]

Problem

When deleting a resource in Radar, the confirmation dialog asks "are you sure?" — but it gives no indication of what else will be affected. Kubernetes garbage collection means deleting a parent resource (e.g. a Deployment, Namespace, or custom resource) can silently remove a cascade of dependent resources along with it.

This is easy to miss, especially for users less familiar with owner references.

Idea

Before confirming a delete, show the user a tree of resources that will be garbage collected as a result — pods, replica sets, config maps, PVCs, etc., depending on what owns what.

The implementation is relatively straightforward: a dry-run delete or an owner-reference traversal from the cache can surface the dependency tree without making any actual changes to the cluster.

Why it matters

It turns an irreversible action into an informed one. Small lift, real safety value — especially as Radar is used by people doing day-to-day cluster operations, not just observation.

[nadaverell]

Shipped — the delete confirmation dialog now shows an expandable tree of dependent resources that will be garbage-collected via owner references (BFS over EdgeManages topology edges).

Closing.