storax/kubedoom
Kill Kubernetes pods by playing Id's DOOM! observed · 2026-08-28
Health v2 · maintenance only
32/100
- Activity 0
- Release rhythm 35
- Longevity 100
Flags: no_releases
How is this computed?
round(0.45*activity + 0.35*rhythm + 0.20*longevity); archived -> min(score, 10) — computed 2026-09-03. Adoption (stars, forks) is never an input.
- gap_med: n/a
- age_days: 2558
- days_rel: n/a
- days_push: 743
- n_releases_24m: 0
Adoption not part of the score
2166 stars · 134 forks observed · 2026-08-28
What it is AI-extracted, prompt v1, taxonomy v1, 2026-08-30, confidence not recorded
Kubedoom is a novelty chaos-engineering tool that lets you kill Kubernetes pods (or namespaces) by shooting them as monsters in a modified version of Id's DOOM, delivered via a containerized VNC session. It is a fork of dockerdoomd/psdoom that maps live pods from your cluster into the game.
Use cases
- kill kubernetes pods by playing doom
- fun chaos engineering tool for kubernetes
- delete pods in a cluster through a game
- clean up too many namespaces interactively
- demo tool for kubernetes meetups
When to choose
- you want a fun, memorable way to delete pods or namespaces in a dev/test cluster
- you want a novelty demo of chaos engineering for a presentation
- you already run kubectl locally and want a game-based pod killer
When to avoid
- production clusters where accidental pod deletion is unacceptable
- you need serious chaos engineering with controlled experiments and metrics
- you cannot run a VNC client or expose port 5901
Facets
application · maturity active
game container-orchestration developer-tools developer-tools gaming-tools go cpp doom chaos-engineering kubectl vnc novelty pod-management containers devops docker kubernetes linux
1 source
- readme: https://github.com/storax/kubedoom · fetched 2026-08-28 · af3dd5abd75b
Member repositories
| Repository | Role | Health v2 |
|---|---|---|
| storax/kubedoom | main | 32 |
For agents
Data as of 2026-08-30T08:39:29.467469+00:00 · Report a problem