Using Chaos Mesh to enhance pegasus's stability

Hello, I am [Chaos Mesh](https://github.com/chaos-mesh/chaos-mesh) maintainer. [Chaos Mesh](https://github.com/chaos-mesh/chaos-mesh) is a open source chaos engineering platform for Kubernetes.

As you may have known, chaos engineering is a promising method that can guarantee system resilience. We have been practicing chaos engineering for long on databases and have found many issues in various fault scernarios (for example data consistency issue caused by excessive recovery time). Some of the issue records at https://github.com/orgs/chaos-mesh/projects/1. There are also [many adopters]( https://github.com/chaos-mesh/chaos-mesh#adopters) who are using [Chaos Mesh](https://github.com/chaos-mesh/chaos-mesh) to test their systems, such as PingCAP, Daily motion, Xpeng Motors, Meituan-Dianping, Apache pulsar, etc.

That said, I would like to invite you to use [Chaos Mesh](https://github.com/chaos-mesh/chaos-mesh) to enhance pegasus's stability. You can directly use [Chaos Mesh](https://github.com/chaos-mesh/chaos-mesh) or integrate it with your test platform. [Chaos Mesh](https://github.com/chaos-mesh/chaos-mesh) supports rich injection methods, such as pod/container kill, network partition, network interruption, CPU/memory usage, time rollback, disk failure, etc.
Welcome to use it to enhance the stability of pegasus. If you have any questions, submit an issue at https://github.com/chaos-mesh/chaos-mesh, or send me an email zhouqiang@pingcap.com

Hope this helps and look forward to further communications. ❤️

The issue does not name Pegasus files, tests, or an integration entry point. Start by reviewing Chaos Mesh's supported fault-injection methods and the linked Chaos Mesh issue records, then define a concrete Pegasus test target and success criteria before implementation.

Written by the indexing model from the issue text.