kube-monkey review
A focused, free tool for scheduled Kubernetes pod-disruption experiments.
Reviewed by iTechGuides Editors · Editorial team · Updated Oct 2026
kube-monkey is an open-source chaos engineering tool for Kubernetes clusters. It randomly deletes opted-in Kubernetes pods to examine how workloads recover from disruption. Teams testing Kubernetes workload resilience can configure weekday experiment windows, mean time between failures, target namespaces, pod kill modes, dry-run behavior, and notifications. Its purpose is deliberately narrow: pod termination rather than a broad library of infrastructure or application faults.
Deployment runs inside a Kubernetes cluster and can be handled manually or through Helm. The self-hosted model suits teams that want source-available software they can operate within their own Kubernetes environment. Targeting controls include Kubernetes labels, namespace blacklists and whitelists, and fixed, percentage-based, random, or all-pod kill modes. These controls help teams limit experiments and preview behavior before enabling pod deletion. Slack webhook and custom API notifications extend the basic workflow without changing its Kubernetes-centered scope.
The project is a practical choice for scheduled pod-disruption exercises, especially when cost and source access matter. It should suit teams that already operate Kubernetes and want configurable workload-recovery experiments with straightforward notification options. Teams seeking cloud failure injection, network failure injection, or a wider chaos-testing platform should choose an alternative with those capabilities. kube-monkey’s value comes from its focused implementation: it addresses Kubernetes pod resilience without presenting itself as a general-purpose failure-injection system.
kube-monkey pros and cons
- Where it wins
- Free and open-source under the Apache License 2.0
- Supports labels, namespaces, dry runs, and multiple kill modes
- Includes Slack webhook and custom API notifications
- Where it doesn't
- Self-hosted deployment requires a Kubernetes cluster
- Injects pod-deletion faults rather than cloud or network failures
- Focused mainly on scheduled workload recovery experiments
kube-monkey fact sheet, pricing and score →
Advertiser disclosure: iTechGuides is reader-supported. Vendors can pay for top positions in our rankings and for a place on other products' pages, and we may earn a commission when you click some links. Bought places stand at the number bought; this page and our disclosure say so. Paying vendors may get a fuller, more detailed review from our editors, and that review can change their score. How we rank.
Last updated · How we research and update