chaos-mesh
reference corpus · status live · domain OPS (Operations and SRE) · lane A · refresh pinned · tags GLOBAL · CHAOS-ENGINEERING · RELIABILITY · KUBERNETES · FAULT-INJECTION
What an agent uses it for
An agent doing chaos engineering on Kubernetes queries this for Chaos Mesh fault-injection CRDs (pod/network/IO/time faults).
curl -fsSLO https://raw.githubusercontent.com/xerj-org/xerj/corpus-hub/tools/xerj-code/hub/chaos-mesh.jsonxerj corpus add --from ./chaos-mesh.jsonxerj corpus index chaos-mesh then xerj code chaos-mesh "your question"Needs the xerj CLI and a local node running; the copy prompt covers both, checks each step, and shows how to stop only the node you started. No shell: the MCP tool xerj_code_search with corpus: "chaos-mesh", once the corpus is indexed on the node.
Sources and pins
| source | pin | licence | size | review note |
|---|---|---|---|---|
| chaos-mesh | 780cb80cc132 | Apache-2.0 | 16.2 MB / 1,170 files | licence host-verified (ok-spdx): Apache-2.0 |
16.2 MB across 1,170 files. Added 2026-10-13.
Rights
Apache-2.0. Redistribution permitted with attribution per the licence review. The review block records a human opening each licence file at the pin. Detector output is a hint, never the verdict.
Retrieval spot-check (G7)
Not yet spot-checked. Queries are pre-registered in the registry before grading.