litmuschaos/chaos-operator

chaos engineering via kubernetes operator

Hosted by Cloud Native Computing Foundation · part of Linux Foundation

View on GitHub ↗Jump to charts ↓

litmuschaos/chaos-operator has 150+ stars and 100+ forks on GitHub, is written in Go, and was last pushed on Jul 15, 2026. Data as of . Signed-in members get hourly updates — create a free account.

Summary Information

Updated 32 minutes ago
Added to GitGenius on October 15th, 2026
Created on April 23rd, 2019
Open Issues & Pull Requests: 17 (+0)
GitHub issues: Enabled
Number of forks: 105
Total Stargazers: 158 (+0)
Total Subscribers: 7 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 180.5 days
Mean response time: 180.5 days
90th percentile: 180.5 days
Tracked items: 1

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 2
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 367 days
Stale 30+ days: 2
Stale 90+ days: 1

Recent activity

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

Top labels

No label distribution available yet.

Most active issues this week

Sign in to see which issues are moving.
Sign in

Detailed Description

Litmus chaos-operator is a Kubernetes operator that automates the injection of chaos experiments into applications and infrastructure for resilience testing and validation.

The tool addresses the challenge of validating application resilience on Kubernetes by automating chaos experiment execution in a managed, standardized way. It works by allowing developers and SREs to annotate applications for chaos testing, then define a ChaosEngine custom resource that describes which experiments to run. The operator reconciles the desired state specified in the ChaosEngine by creating and managing runner pods that execute the chaos experiments. The approach leverages the Operator-SDK framework to implement standard Kubernetes operator patterns, where the operator watches for changes to ChaosEngine resources and takes action to implement the specified chaos workflows.

Teams should adopt this tool if they need structured, repeatable chaos engineering workflows on Kubernetes. It suits organizations running stateless or stateful applications that want to validate resilience without manual experiment management. The tool provides categorized chaos bundles for different application types and infrastructure components, standardized experiment specifications, and the ability to run chaos as a background service based on application annotations. It also supports test-run resiliency and allows retention or cleanup of chaos resources after experiments complete.

The project maintains active development with regular commits across its codebase. The maintainers respond to issues and pull requests consistently, indicating ongoing engagement with the community. The project accepts contributions from external developers and maintains organized issue tracking for bug reports and feature requests.