Litmus
3.28.0ObservabilityLitmus 3.28.0 is a focused maintenance release fixing a probe config leak, a subscriber crash on workflow events, and a Python vulnerability in the frontend base image.
securityUpgrade frontend to resolve Python CVE in base image
The frontend container was running on a ubi8 base image with a Python vulnerability. The fix upgrades it to ubi9. If you run Litmus in environments with strict image scanning policies (e.g., Trivy in CI, ACS, or Prisma), this upgrade will clear those alerts. Pull the 3.28.0 frontend image and redeploy — no config changes needed.
breakingProbe config leak fix may change behavior for shared-type probe setups
If you run multiple probes of the same type in a single experiment, previous releases silently shared stale config between them. The fix now isolates config per probe. Audit any experiments where multiple probes of the same type are defined — if you were unknowingly relying on config bleed-over, results may differ after upgrading.
enhancementSubscriber crash fix improves reliability for GitOps and event-driven workflows
Teams using Litmus in GitOps mode or triggering experiments via Argo Workflow ADD events with ChaosEngine nodes were hitting silent subscriber crashes. After upgrading to 3.28.0, those workflows should resume without manual subscriber restarts. No action required beyond the upgrade, but verify subscriber pod stability post-deploy if you've been seeing unexplained restarts.
Key changes (5)
- Fixed stale config leak across multiple probes of the same type — this could cause probes to incorrectly inherit config from a previous probe run
- Subscriber no longer crashes when Workflow ADD events contain ChaosEngine nodes, improving experiment reliability
- Frontend base image upgraded from ubi8 to ubi9, resolving a known Python vulnerability
- Fixed image registry bug when editing or cloning experiments in Litmus Checker
- Canonical added as an official adopter