Litmus
Cloud-native chaos engineering framework declaring chaos scenarios as Kubernetes custom resources.
- Provider
- default
- Kind
- Worker
- Category
- Compute
- Official docs
- https://docs.litmuschaos.io/
| property | type | values | required | kind default | this component |
|---|---|---|---|---|---|
| accelerator | enum | none | gpu | asic | no | none | inherited |
| concurrency | integer | — | no | — | inherited |
| declarativeCustomResources | boolean | — | no | true | inherited |
| fanoutStrategy | enum | none | push | pull | hybrid | no | none | inherited |
| fanoutThreshold | integer | — | no | — | inherited |
| faultSource | enum | chaos-hub | custom | no | — | inherited |
| idempotent | boolean | — | no | false | ▸ false |
| instances | integer | — | no | — | inherited |
| managed | boolean | — | no | false | ▸ false |
| rateControl | enum | none | fixed | aimd | no | none | inherited |
| schedule | string | — | no | — | inherited |
| trigger | enum | queue | stream | schedule | batch | manual | yes | — | ▸ manual |
Every rule whose selector covers this component's kind or its category. Whether a rule fires depends on the design: its properties, its edges and its groups.
Pure push fan-out over a social graph is brutal at the tail: one post from an account with millions of followers becomes millions of cache writes. A follower threshold above which readers merge at read time bounds that write amplification.
- — all of these hold:
- — the node's `fanoutStrategy` is "push"
- — the node's `fanoutThreshold` has no value
- — the design contains a node of kind graph-database
One worker pool consuming several queues lets a slow or poisoned queue starve the others. That is precisely what the design's per-queue isolation requirement forbids.
- — all of these hold:
- — the node has more than 1 incoming edge from a queue
- — the design requirement `isolation.perQueue` is true
A stateful compute node pinned to exactly one availability zone disappears with that zone, and its state goes with it. Nodes inside a cell are exempt, because there the cell is deliberately single-zone and redundancy comes from the other cells.
- — all of these hold:
- — the node's `stateless` is false
- — the node sits inside exactly 1 availability-zone group
- — this does not hold:
- — the node sits inside at least one cell group
nodes:
- { id: "litmus", component: "litmus" }# yaml-language-server: $schema=../../schema/component.schema.json # Litmus: CNCF cloud-native chaos engineering framework. Chaos intent is declared in Kubernetes custom # resources, and a chaos scenario is "much more than a simple chaos experiment" - it also defines the # expected result and observes the outcome. Faults come from the prebuilt hub or are written by the # team ("What is Litmus?"). schemaVersion: "1" type: "component" id: "litmus" kind: "worker" provider: "default" docs: "https://docs.litmuschaos.io/" defaults: managed: false trigger: "manual" idempotent: false properties: faultSource: type: "enum" values: ["chaos-hub", "custom"] declarativeCustomResources: type: "boolean" default: true