Resource Dependency Graph Generator

Before changing a ConfigMap or deleting a Secret it helps to know what depends on it. The Resource Dependency Graph Generator reads several pasted manifests and draws the cross-resource references: workloads to their ServiceAccount, ConfigMaps and Secrets; Services to the pods they select; Ingress to Services; and RBAC bindings to subjects and roles.

Missing references are flagged so you can catch dangling dependencies. Everything runs locally; nothing is uploaded.

• Workloads - to ServiceAccount, ConfigMap, Secret, PVC.
• Services - to selected workloads.
• Ingress - to backend Services.
• RBAC - bindings to subjects and roles.
• Missing refs - dangling references flagged.
• Copy / Download / Print - export the graph.

1. Paste several manifests (with --- between them).
2. Generate the dependency graph.
3. Inspect who depends on what.

Example 1 - config. Deployment -> ConfigMap (volume), Deployment -> ServiceAccount.

Example 2 - traffic. Ingress -> Service -> Deployment.

• Impact analysis - know what breaks if a resource changes.
• Find dangling refs - missing targets flagged.
• Local - nothing uploaded.
• Exportable - copy, download or print.