# storax/kubedoom

Kill Kubernetes pods by playing Id's DOOM!

Repository: https://github.com/storax/kubedoom
Canonical: https://ross.abutalabs.com/products/kubedoom
Language: C++
License: GPL-3.0
License Family: copyleft
Topics: doom, kubernetes, kubectl, go, golang, c, kind, docker, dockerfile, pods
Last push: 2024-08-20T22:12:53+00:00

## Health v2 (maintenance only)
Score: 32/100 (v2, computed 2026-09-03T02:20:16.233290+00:00)
- activity 0, release rhythm 35, longevity 100
- inputs: {"age_days": 2558, "days_push": 743, "days_rel": null, "gap_med": null, "n_releases_24m": 0}
- flags: no_releases
- formula: round(0.45*activity + 0.35*rhythm + 0.20*longevity); archived -> min(score, 10)

## Adoption (not part of the score)
Stars 2166, forks 134 (observed 2026-08-28T04:06:21.382127+00:00)

## What it is
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
- artifact type: application
- maturity: active
- function: game, container-orchestration, developer-tools
- domain: developer-tools, gaming-tools
- platform: go, cpp
- tags: doom, chaos-engineering, kubectl, vnc, novelty, pod-management, containers, devops, docker, kubernetes, linux

## Member repositories
- storax/kubedoom (main) score 32

## Provenance
- Observed fields: from GitHub, fetched 2026-08-28T04:06:21.382127+00:00.
- Health v2: computed from the inputs above; adoption is never an input.
- Inferred fields (summary, facets, guidance): AI-extracted, prompt v1, taxonomy v1, on 2026-08-30T02:49:57.474199+00:00, confidence not recorded.
  - readme: https://github.com/storax/kubedoom (fetched 2026-08-28T04:06:21.382127+00:00, sha af3dd5abd75b)
- Data as of 2026-08-30T08:39:29.467469+00:00.