Show HN: Kroot – dependency-graph root cause analysis for Kubernetes (opens in new tab)

(github.com)

1 pointsAn0n_Jon17d ago1 comments

1 comments

Hi HN — I built kroot to help debug Kubernetes failures by tracing dependencies between resources.

Instead of only showing symptoms (CrashLoopBackOff, etc), it builds a dependency graph of cluster resources and tries to answer:

"Why did this actually break?"

Example failure chain it can detect:

Secret/prod/db-password missing ↓ Pod/prod/payments-api CrashLoopBackOff ↓ Service/prod/payments has no endpoints ↓ Ingress returning 503

Would love feedback from people running Kubernetes in production.

j / k navigate · click thread line to collapse

An0n_JonOP17d ago

Hi HN — I built kroot to help debug Kubernetes failures by tracing dependencies between resources.

Instead of only showing symptoms (CrashLoopBackOff, etc), it builds a dependency graph of cluster resources and tries to answer:

"Why did this actually break?"

Example failure chain it can detect:

Secret/prod/db-password missing ↓ Pod/prod/payments-api CrashLoopBackOff ↓ Service/prod/payments has no endpoints ↓ Ingress returning 503

Would love feedback from people running Kubernetes in production.

j / k navigate · click thread line to collapse