a81d084c93
* fix: validate container_name in container scenario plugin The container scenario plugin removed pods and incremented killed_count even when the requested container_name was never found, causing scenarios to silently report success with no disruption (issue #1409). Track whether a container was actually found and killed; only increment killed_count on a real kill, skip pods that lack the target container, and raise a clear RuntimeError once all pods are exhausted without a kill. Adds unit tests covering invalid, valid, empty, heterogeneous, and count-exceeds-target scenarios. Closes #1409 * fix: report actual kill count in container-not-found error When the candidate pod list is exhausted without finding the target container, the RuntimeError now reports how many containers were actually killed ("N of M requested container(s) were killed") instead of always claiming "No containers were killed", which was inaccurate in partial-success cases. * fix: only raise container-not-found error when nothing was killed Address review feedback: the "not found in any matching pod" error was raised even after one or more containers had already been killed (when count exceeds the number of pods containing the target), making the message contradictory. Now that error only fires when killed_count == 0. When some kills already happened but the candidate list is exhausted, the loop falls through to the existing "Trying to kill more containers than were found" error, which accurately describes that case. --------- Co-authored-by: augmentcode[bot] <185243770+augmentcode[bot]@users.noreply.github.com> Co-authored-by: Darshan Jain <darjain@redhat.com>
Krkn aka Kraken
Chaos and resiliency testing tool for Kubernetes. Kraken injects deliberate failures into Kubernetes clusters to check if it is resilient to turbulent conditions.
Workflow
How to Get Started
Instructions on how to setup, configure and run Kraken can be found in the documentation.
Blogs, podcasts and interviews
Additional resources, including blog posts, podcasts, and community interviews, can be found on the website
Roadmap
Enhancements being planned can be found in the roadmap.
Contributing
We are always looking for more enhancements, fixes to make it better, any contributions are most welcome. Feel free to report or work on the issues filed on github.
See CONTRIBUTING.md for details, or check the contribution guidelines on the website.
Community
Key Members(slack_usernames/full name): paigerube14/Paige Rubendall, mffiedler/Mike Fiedler, tsebasti/Tullio Sebastiani, yogi/Yogananth Subramanian, sahil/Sahil Shah, pradeep/Pradeep Surisetty and ravielluri/Naga Ravi Chaitanya Elluri.
Community Meeting
If you have any questions that you think could be better discussed on a meeting, we have monthly office hours. Please add items to the agenda beforehand so we can best prepare to help you.
The Linux Foundation® (TLF) has registered trademarks and uses trademarks. For a list of TLF trademarks, see Trademark Usage.