Litmus
3.27.0ObservabilityLitmus 3.27.0 ships Job targeting for chaos experiments and fixes a cluster of stability bugs: nil pointer crashes, GitOps deadlocks, race conditions, and probe detection failures.
enhancementTarget Kubernetes Jobs in chaos experiments
If your team runs batch workloads or CI pipelines as Kubernetes Jobs, you can now inject chaos directly into them. Update your experiment manifests to reference Job resources and validate resilience of batch processing paths — something previously impossible without workarounds.
breakingGitOps two-way sync was silently broken — verify your sync state after upgrading
The GitOps sync handler goroutine was disabled, meaning changes in Git were not propagating back to Litmus in two-way mode. After upgrading to 3.27.0, manually trigger a sync and confirm experiment state matches your Git source of truth. Any drift that accumulated should be reconciled.
enhancementMultiple nil pointer and race condition fixes reduce silent failures
At least three separate nil pointer dereferences are fixed in this release (subscriber, QueryServerVersion, YAML parser), plus experiment run race conditions. If you've seen intermittent crashes or experiments stuck in inconsistent states, upgrading is the straightforward fix — no config changes needed.
主な変更 (5)
- New: Kubernetes Jobs can now be targeted in chaos experiments, expanding workload coverage beyond Deployments and StatefulSets
- 503 returned when MongoDB is down, enabling probes to correctly detect infrastructure failures instead of hanging
- Subscriber crash on Workflow ADD events (nil pointer dereference) fixed — previously could silently break experiment scheduling
- GitOps deadlock in GitMutexLock.Unlock resolved, and the GitOps sync handler goroutine re-enabled to restore two-way sync
- CMD probe command limit raised from 1024 characters, unblocking complex probe scripts