Problem
GitOps mode works well for managing Chaos Experiments as code, but Resilience Probes are completely left out of the picture. Since Litmus 3.0, probes are standalone, reusable first-class resources, decoupled from experiments by design. Yet the only way to create or update them is through the ChaosCenter UI or API. There's no way to declare them in the GitOps repo and have them synced in automatically, which makes it impossible to fully manage a chaos engineering setup in a declarative, GitOps-native way.
Our Use Case
We have an AI agent that generates both Chaos Experiment and Resilience Probe manifests and commits them to a GitOps repository. The intended flow is:
AI Agent → GitOps Repo → LitmusChaos GitOps Sync → ChaosCenter
The experiment half works great. But because probes aren't covered by the GitOps sync, they have to be created separately via the API — which breaks the fully automated, hands-off flow we're building toward. Ideally, an agent (or a human, via a PR) should be able to commit a probe manifest to the repo and have it show up in ChaosCenter automatically, ready to be referenced by experiments.
What We'd Love to See
- Repo → ChaosCenter sync (priority): probe manifests committed to the GitOps repo are picked up by the GitOps agent and create/update the corresponding probes in ChaosCenter — consistent with how experiments are handled today.
- ChaosCenter → Repo sync (nice to have): probes created via the UI or API are written back to the repo, completing the bidirectional sync.
This would unlock a fully declarative chaos engineering workflow where experiments and their associated probes are version-controlled, auditable via Git history, and deployable through standard GitOps tooling.
References
Problem
GitOps mode works well for managing Chaos Experiments as code, but Resilience Probes are completely left out of the picture. Since Litmus 3.0, probes are standalone, reusable first-class resources, decoupled from experiments by design. Yet the only way to create or update them is through the ChaosCenter UI or API. There's no way to declare them in the GitOps repo and have them synced in automatically, which makes it impossible to fully manage a chaos engineering setup in a declarative, GitOps-native way.
Our Use Case
We have an AI agent that generates both Chaos Experiment and Resilience Probe manifests and commits them to a GitOps repository. The intended flow is:
The experiment half works great. But because probes aren't covered by the GitOps sync, they have to be created separately via the API — which breaks the fully automated, hands-off flow we're building toward. Ideally, an agent (or a human, via a PR) should be able to commit a probe manifest to the repo and have it show up in ChaosCenter automatically, ready to be referenced by experiments.
What We'd Love to See
This would unlock a fully declarative chaos engineering workflow where experiments and their associated probes are version-controlled, auditable via Git history, and deployable through standard GitOps tooling.
References