// the take
KubeInvaders turns chaos engineering into a Space Invaders-style game: pods and nodes are aliens, and shooting them kills the underlying Kubernetes resource so you can watch how your cluster reacts. It's aimed at platform/SRE teams who want a visual, teachable way to run resilience tests or demo chaos engineering at conferences and training sessions, rather than teams looking for a scriptable chaos-testing framework.
The built-in KWOK-powered demo cluster means you can try the whole thing with one `docker run` and no real cluster, which is a genuinely low-friction way to evaluate it before pointing it at anything real. It ships Prometheus metrics and a ready-made Grafana dashboard, so chaos sessions are actually observable rather than just a UI with no data trail. Node and pod chaos aren't the whole story either — there's a separate chaos-exec/chaos-node image set with Lua-driven 'programming mode' and per-target Python scripts (Postgres, Kafka, Vault, Consul, etc.), so it reaches past basic pod deletion into app-level fault injection.
There's no supported Helm chart — the README says so outright — so deploying it into a real cluster means hand-rolling RBAC and a Deployment yourself; the chart in the repo is a legacy artifact pinned to v1.9.7. The auth model is a single long-lived ServiceAccount token that you either paste into a web form or pass as a plain env var, with `DISABLE_TLS`/`INSECURE_ENDPOINT` flags readily available to skip API server cert verification — fine for a demo, risky if someone reuses that pattern against a staging or prod cluster. This is also a tool whose entire purpose is deleting real pods and nodes from a browser game, and there's no visible safeguard layer (dry-run, confirmation, scoped blast-radius limits) beyond 'configure the namespaces you want it to touch' — the RBAC manifest is the only thing standing between a misclick and an outage. Most of the project's real-world validation comes from conference talks and blog posts going back to 2019 rather than current test coverage, so it's hard to judge how actively the chaos-exec scripts and node-chaos path are maintained today.
We read the README, the directory tree and a key source file in October 2026. Nobody pays to be listed. How we judge →