chaos-mesh VS kubernetes-operator

Ive been messing around with chaos mesh recently (https://chaos-mesh.org/) and im wondering: is there any way i can define custom behaviour in one of my experiments? Specifically, I want to deploy a Pod with a certain image using an experiment.

Litmus, Gremlin, Chaos Mesh, and Chaos Monkey are all popular open-source tools used for chaos engineering. As we will be using AWS cloud infrastructure, we will also explore AWS Fault Injection Simulator (FIS). While they share the same goals of testing and improving the resilience of a system, there are some differences between them. Here are some comparisons:

https://chaos-mesh.org/ (open source)

Implement Chaos Mesh and Litmus chaos engineering framework to understand the behavior and stability of application in real-world use cases.

Here is our recent experience with Chaos Mesh for performing basic chaos engineering experiments on an application in Kubernetes.

In March 2018, an article titled Service Mesh is the broad trend, what about Database Mesh?, was pubslished on InfoQ China and went viral in the technical community. In this article, Zhang Liang, the founder of Apache ShardingSphere, described Database Mesh concept along with the idea of Service Mesh. Four years later, the Database Mesh concept has been integrated by several companies together with their own tools and ecosystems. Today, in addition to Service Mesh, a variety of “X Mesh” concepts such as ChaosMesh, EventMesh, IOMesh have emerged. Following four years of development, Database Mesh has also started a new chapter: Database Mesh 2.0.

🐒 Chaos Mesh will turn 2 on 2021.12.31! We're grateful for every contribution that helped this project grow, and we’d like to hear your Chaos Mesh story!

So i came across this recently, haven't used it myself but it seems to fit your requirements: https://github.com/chaos-mesh/chaos-mesh

Recently though, I've seen some awesome packaging of jenkins into a stateless beast that is DRY AF and configurable to the N-th degree. Do your engineering squads argue about which plugins to install, syntax to use or even methods of authenticating into the jenkins instance? Fine give them their own instance... all managed via jenkins-operator in your k8s cluster (as an example).

Possible options considered; Run Jenkins on a master and worker build server on EC2 Run Jenkinsci on Kubernetes with https://github.com/jenkinsci/kubernetes-operator

You mean this operator? https://github.com/jenkinsci/kubernetes-operator