asobti/kube-monkey

An implementation of Netflix's Chaos Monkey for Kubernetes clusters

View on GitHub ↗Jump to charts ↓Open shareable report →

asobti/kube-monkey has 3k+ stars and 250+ forks on GitHub, is written in Go, and was last pushed on Sep 20, 2026. Data as of . Signed-in members get hourly updates — create a free account.

Summary Information

Updated 1 hour ago
Added to GitGenius on September 22nd, 2026
Created on December 8th, 2016
Open Issues & Pull Requests: 5 (+0)
GitHub issues: Enabled
Number of forks: 258
Total Stargazers: 3,083 (+0)
Total Subscribers: 53 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 35.5 days
Mean response time: 866.2 days
90th percentile: 2341.5 days
Tracked items: 16

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 0
New in 7 days: 0
Closed in 7 days: 0
Avg open age: N/A days
Stale 30+ days: 0
Stale 90+ days: 0

Recent activity

Opened in 7 days: 0
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 0

Top labels

  • enhancement (1)

Most active issues this week

Sign in to see which issues are moving.
Sign in

Detailed Description

kube-monkey is a chaos engineering tool that implements Netflix's Chaos Monkey for Kubernetes clusters.

The tool addresses the need to validate that services can survive unexpected failures by randomly terminating pods within a cluster. Applications opt in through Kubernetes labels, and operators define windows of time during which terminations should occur. Dry run mode is enabled by default, allowing teams to observe the tool's behavior before it actually deletes pods in production environments.

Teams should adopt kube-monkey if they want to systematically test the resilience of their Kubernetes workloads without manual intervention. It suits any organization running stateless or properly replicated services that should tolerate pod loss. The tool is particularly valuable for catching configuration issues where services lack proper health checks or replica counts. Adoption requires only adding a label to the apps you want to test and configuring the schedule and kill modes through the documentation.

The project maintains active documentation covering installation, configuration, and operational concerns including Prometheus metrics and Slack notifications. Development activity shows consistent attention to the codebase with regular updates addressing both new features and maintenance needs. The project accepts community contributions and maintains a dedicated communication channel for users and developers.