---
title: Intelligent Dependency Graphs
slug: intelligent-dependency-graphs
createdAt: 2026-02-24T04:09:12.655Z
---

# Overview

Kubegrade provides deep cluster visualization and dependency mapping to help teams understand relationships, blast radius, and warning states quickly.

![](https://api.archbee.com/api/optimize/7Lzjl4NBI_sc1o8F1zL-G/sfJ59I3Q-dhp--SKz0ZJK-20260430-064853.gif)



# Object-level graph model

Kubegrade’s graph models relationships such as:

- Namespace → workload (Deployment/StatefulSet/DaemonSet)
- Workload → pods
- Service → endpoints/pods
- Ingress → services
- ConfigMap/Secret references
- NetworkPolicy relationships
- Storage dependencies (PVC/PV)
- Optional external dependencies (via integrations/annotations)

Purpose:

- Faster root cause analysis
- Change impact assessment
- Upgrade dependency planning



# Filters and scopes

## Filters

- Cluster / environment
- Object kind
- Cluster wide objects
- Namespace



## Scopes

Users should be able to graph:

- Full cluster
- Namespace only
- Incident-specific objects
- Nested objects



# Warning states + “what changed” views

## Warning states

Overlay graph nodes/edges with states such as:

- Degraded
- Pending / unschedulable
- Failed probes
- Policy violation
- Drift detected
- Upgrade blocker



## “What changed” views

Compare graph snapshots over time to identify:

- New/removed dependencies
- Routing changes
- Config-linked impact
- Service endpoint shifts

This is especially useful for post-incident reviews and upgrade regressions.



# Sharing and exporting views

## Sharing

- Link-based internal sharing (RBAC-respected)
- Saved workspace/project views
- Embed in incident tickets/docs 



## Exporting

- Image export (PNG/SVG)
- Data export (JSON graph metadata)
- Snapshot attachment to incident reports