[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"project-9905":3},{"id":4,"name":5,"fullName":6,"owner":5,"repo":5,"description":7,"homepage":8,"htmlUrl":9,"language":10,"languages":9,"totalLinesOfCode":9,"stars":11,"forks":12,"watchers":13,"openIssues":14,"contributorsCount":15,"subscribersCount":15,"size":15,"stars1d":16,"stars7d":17,"stars30d":18,"stars90d":15,"forks30d":15,"starsTrendScore":19,"compositeScore":20,"rankGlobal":9,"rankLanguage":9,"license":21,"archived":22,"fork":22,"defaultBranch":23,"hasWiki":24,"hasPages":22,"topics":25,"createdAt":9,"pushedAt":9,"updatedAt":38,"readmeContent":39,"aiSummary":40,"trendingCount":15,"starSnapshotCount":15,"syncStatus":16,"lastSyncTime":41,"discoverSource":42},9905,"chaos-mesh","chaos-mesh\u002Fchaos-mesh","A Chaos Engineering Platform for Kubernetes.","https:\u002F\u002Fchaos-mesh.org",null,"Go",7743,1003,119,462,0,2,13,78,12,40.01,"Apache License 2.0",false,"master",true,[26,27,28,5,29,30,31,32,33,34,35,36,37],"chaos","chaos-engineering","chaos-experiments","chaos-testing","cloud-native","cncf","fault-injection","golang","kubernetes","microservices","operator","site-reliability-engineering","2026-06-12 02:02:14","\u003Cimg src=\"static\u002Flogo.svg#gh-light-mode-only\" alt=\"Chaos Mesh Logo\" width=\"450\"\u002F>\n\u003Cimg src=\"static\u002Flogo-white.svg#gh-dark-mode-only\" alt=\"Chaos Mesh Logo\" width=\"450\"\u002F>\n\n---\n\n\u003C!-- markdown-link-check-disable -->\n\n[![LICENSE](https:\u002F\u002Fimg.shields.io\u002Fgithub\u002Flicense\u002Fchaos-mesh\u002Fchaos-mesh.svg)](https:\u002F\u002Fgithub.com\u002Fchaos-mesh\u002Fchaos-mesh\u002Fblob\u002Fmaster\u002FLICENSE)\n[![codecov](https:\u002F\u002Fcodecov.io\u002Fgh\u002Fchaos-mesh\u002Fchaos-mesh\u002Fbranch\u002Fmaster\u002Fgraph\u002Fbadge.svg)](https:\u002F\u002Fcodecov.io\u002Fgh\u002Fchaos-mesh\u002Fchaos-mesh)\n[![Go Report Card](https:\u002F\u002Fgoreportcard.com\u002Fbadge\u002Fgithub.com\u002Fchaos-mesh\u002Fchaos-mesh)](https:\u002F\u002Fgoreportcard.com\u002Freport\u002Fgithub.com\u002Fchaos-mesh\u002Fchaos-mesh)\n[![GoDoc](https:\u002F\u002Fimg.shields.io\u002Fbadge\u002FGodoc-reference-blue.svg)](https:\u002F\u002Fgodoc.org\u002Fgithub.com\u002Fchaos-mesh\u002Fchaos-mesh)\n[![Upload Image](https:\u002F\u002Fgithub.com\u002Fchaos-mesh\u002Fchaos-mesh\u002Factions\u002Fworkflows\u002Fupload_image.yml\u002Fbadge.svg?event=schedule)](https:\u002F\u002Fgithub.com\u002Fchaos-mesh\u002Fchaos-mesh\u002Factions\u002Fworkflows\u002Fupload_image.yml)\n\n[![FOSSA Status](https:\u002F\u002Fapp.fossa.com\u002Fapi\u002Fprojects\u002Fgit%2Bgithub.com%2Fchaos-mesh%2Fchaos-mesh.svg?type=shield)](https:\u002F\u002Fapp.fossa.com\u002Fprojects\u002Fgit%2Bgithub.com%2Fchaos-mesh%2Fchaos-mesh?ref=badge_shield)\n[![CII Best Practices](https:\u002F\u002Fbestpractices.coreinfrastructure.org\u002Fprojects\u002F3680\u002Fbadge)](https:\u002F\u002Fbestpractices.coreinfrastructure.org\u002Fprojects\u002F3680)\n[![Artifact Hub](https:\u002F\u002Fimg.shields.io\u002Fendpoint?url=https%3A%2F%2Fartifacthub.io%2Fbadge%2Frepository%2Fchaos-mesh)](https:\u002F\u002Fartifacthub.io\u002Fpackages\u002Fhelm\u002Fchaos-mesh\u002Fchaos-mesh)\n\n\u003C!-- markdown-link-check-enable -->\n\nChaos Mesh is an open source cloud-native Chaos Engineering platform. It offers various types of fault simulation and has an enormous capability to orchestrate fault scenarios.\n\nUsing Chaos Mesh, you can conveniently simulate various abnormalities that might occur in reality during the development, testing, and production environments and find potential problems in the system. To lower the threshold for a Chaos Engineering project, Chaos Mesh provides you with a visualization operation. You can easily design your Chaos scenarios on the Web UI and monitor the status of Chaos experiments.\n\n![cncf_logo](.\u002Fstatic\u002Fcncf.png#gh-light-mode-only)\n![cncf_logo](.\u002Fstatic\u002Fcncf-white.png#gh-dark-mode-only)\n\nChaos Mesh is a [Cloud Native Computing Foundation (CNCF)](https:\u002F\u002Fwww.cncf.io\u002F) incubating project. If you are an organization that wants to help shape the evolution of technologies that are container-packaged, dynamically-scheduled and microservices-oriented, consider joining the CNCF. For details about who's involved and how Chaos Mesh plays a role, read the CNCF [announcement](https:\u002F\u002Fwww.cncf.io\u002Fannouncements\u002F2020\u002F09\u002F02\u002Fcloud-native-computing-foundation-announces-tikv-graduation\u002F).\n\n---\n\nAt the current stage, Chaos Mesh has the following components:\n\n- **Chaos Operator**: the core component for chaos orchestration. Fully open sourced.\n- **Chaos Dashboard**: a Web UI for managing, designing, monitoring Chaos Experiments.\n\nSee the following demo video for a quick view of Chaos Mesh:\n\n[![Watch the video](.\u002Fstatic\u002Fdemo.gif)](https:\u002F\u002Fwww.youtube.com\u002Fwatch?v=ifZEwdJO868)\n\n## Chaos Operator\n\nChaos Operator injects chaos into the applications and Kubernetes infrastructure in a manageable way, which provides easy, custom definitions for chaos experiments and automatic orchestration. There are two components at play:\n\n**Chaos Controller Manager**: is primarily responsible for the scheduling and management of Chaos experiments. This component contains several CRD Controllers, such as Workflow Controller, Scheduler Controller, and Controllers of various fault types.\n\n**Chaos Daemon**: runs as DaemonSet and has Privileged permission by default (which can be disabled). This component mainly interferes with specific network devices, file systems, kernels by hacking into the target Pod Namespace.\n\n![Chaos Operator](.\u002Fstatic\u002Fchaos-mesh.png)\n\nChaos Operator uses [CustomResourceDefinition (CRD)](https:\u002F\u002Fkubernetes.io\u002Fdocs\u002Ftasks\u002Faccess-kubernetes-api\u002Fcustom-resources\u002Fcustom-resource-definitions\u002F) to define chaos objects.\n\nThe current implementation supports a few types of CRD objects for fault injection, namely `PodChaos`, `NetworkChaos`, `IOChaos`, `TimeChaos`, `StressChaos`, and so on.\nYou can get the full list of CRD objects and their specifications in the [Chaos Mesh Docs](https:\u002F\u002Fchaos-mesh.org\u002Fdocs\u002F).\n\n## Quick start\n\nSee [Quick Start](https:\u002F\u002Fchaos-mesh.org\u002Fdocs\u002Fquick-start) and [Install Chaos Mesh using Helm](https:\u002F\u002Fchaos-mesh.org\u002Fdocs\u002Fproduction-installation-using-helm\u002F).\n\n## Contributing\n\nSee the [contributing guide](.\u002FCONTRIBUTING.md) and [development guide](https:\u002F\u002Fchaos-mesh.org\u002Fdocs\u002Fdeveloper-guide-overview).\n\n## Adopters\n\nSee [ADOPTERS](ADOPTERS.md).\n\n## Blogs\n\nBlogs on Chaos Mesh design & implementation, features, chaos engineering, community updates, etc. See [Chaos Mesh Blogs](https:\u002F\u002Fchaos-mesh.org\u002Fblog). Here are some recommended ones for you to start with:\n\n- [Chaos Mesh 2.0: To a Chaos Engineering Ecology](https:\u002F\u002Fchaos-mesh.org\u002Fblog\u002Fchaos-mesh-2.0-to-a-chaos-engineering-ecology\u002F)\n- [Chaos Mesh - Your Chaos Engineering Solution for System Resiliency on Kubernetes](https:\u002F\u002Fchaos-mesh.org\u002Fblog\u002Fchaos_mesh_your_chaos_engineering_solution\u002F)\n- [Run Your First Chaos Experiment in 10 Minutes](https:\u002F\u002Fchaos-mesh.org\u002Fblog\u002Frun_your_first_chaos_experiment\u002F)\n- [How to Simulate I\u002FO Faults at Runtime](https:\u002F\u002Fchaos-mesh.org\u002Fblog\u002Fhow-to-simulate-io-faults-at-runtime\u002F)\n- [Simulating Clock Skew in K8s Without Affecting Other Containers on the Node](https:\u002F\u002Fchaos-mesh.org\u002Fblog\u002Fsimulating-clock-skew-in-k8s-without-affecting-other-containers-on-node\u002F)\n- [Building an Automated Testing Framework Based on Chaos Mesh and Argo](https:\u002F\u002Fchaos-mesh.org\u002Fblog\u002Fbuilding_automated_testing_framework)\n\n## Community\n\nPlease reach out for bugs, feature requests, and other issues via:\n\n- Following us on Twitter [@chaos_mesh](https:\u002F\u002Ftwitter.com\u002Fchaos_mesh).\n\n- Joining the `#project-chaos-mesh` channel in the [CNCF Slack](https:\u002F\u002Fslack.cncf.io\u002F) workspace.\n\n- Filling an issue or opening a PR against this repository.\n\n### Community meetings\n\n- Chaos Mesh Community Monthly (Community and project-level updates, community sharing\u002Fdemo, office hours)\n  - Time: on the fourth Thursday of every month (unless otherwise specified)\n  - [RSVP here](https:\u002F\u002Fcommunity.cncf.io\u002Fchaos-mesh-community\u002F)\n  - [Meeting minutes](https:\u002F\u002Fdocs.google.com\u002Fdocument\u002Fd\u002F1H8IfmhIJiJ1ltg-XLjqR_P_RaMHUGrl1CzvHnKM_9Sc\u002Fedit?usp=sharing)\n\n- Chaos Mesh Development Meeting (Releases, roadmap\u002Ffeatures\u002FRFC planning and discussion, issue triage\u002Fdiscussion, etc)\n  - Time: Every other Tuesday (unless otherwise specified)\n  - [RSVP here](https:\u002F\u002Fcommunity.cncf.io\u002Fchaos-mesh-community\u002F)\n  - [Meeting minutes](https:\u002F\u002Fdocs.google.com\u002Fdocument\u002Fd\u002F1s9X6tTOy3OGZaLDZQesGw1BNOrxQfWExjBFIn5irpPE\u002Fedit)\n\n### Community blogs\n\n- Grant Tarrant-Fisher: [Integrate your Reliability Toolkit with Your World](https:\u002F\u002Fmedium.com\u002Fsearch?q=Integrate+your+Reliability+Toolkit+with+Your+World)\n- Yoshinori Teraoka: [Streake: Chaos Mesh によるカオスエンジニアリング](https:\u002F\u002Fmedium.com\u002Fsreake-jp\u002Fchaos-mesh-%E3%81%AB%E3%82%88%E3%82%8B%E3%82%AB%E3%82%AA%E3%82%B9%E3%82%A8%E3%83%B3%E3%82%B8%E3%83%8B%E3%82%A2%E3%83%AA%E3%83%B3%E3%82%B0-46fa2897c742)\n- Sébastien Prud'homme: [Chaos Mesh : un générateur de chaos pour Kubernetes](https:\u002F\u002Fwww.cowboysysop.com\u002Fpost\u002Fchaos-mesh-un-generateur-de-chaos-pour-kubernetes\u002F)\n- Craig Morten\n  - [K8s Chaos Dive: Chaos-Mesh Part 1](https:\u002F\u002Fdev.to\u002Fcraigmorten\u002Fk8s-chaos-dive-2-chaos-mesh-part-1-2i96)\n  - [K8s Chaos Dive: Chaos-Mesh Part 2](https:\u002F\u002Fdev.to\u002Fcraigmorten\u002Fk8s-chaos-dive-chaos-mesh-part-2-536m)\n- Ronak Banka: [Getting Started with Chaos Mesh and Kubernetes](https:\u002F\u002Fitnext.io\u002Fgetting-started-with-chaos-mesh-and-kubernetes-bfd98d25d481)\n- kondoumh: [​Kubernetes ネイティブなカオスエンジニアリングツール Chaos Mesh を使ってみる](https:\u002F\u002Fblog.kondoumh.com\u002Fentry\u002F2020\u002F10\u002F23\u002F123431)\n- Vadim Tkachenko: [ChaosMesh to Create Chaos in Kubernetes](https:\u002F\u002Fwww.percona.com\u002Fblog\u002F2020\u002F11\u002F05\u002Fchaosmesh-to-create-chaos-in-kubernetes\u002F)\n- Hui Zhang: [How a Top Game Company Uses Chaos Engineering to Improve Testing](https:\u002F\u002Fchaos-mesh.org\u002Fblog\u002Fhow-a-top-game-company-uses-chaos-engineering-to-improve-testing)\n- Anurag Paliwal\n  - [Securing tenant services while using chaos mesh using OPA](https:\u002F\u002Fanuragpaliwal-93749.medium.com\u002Fsecuring-tenant-services-while-using-chaos-mesh-using-opa-3ae80c7f4b85)\n  - [Securing namespaces using restrict authorization feature in chaos mesh](https:\u002F\u002Fanuragpaliwal-93749.medium.com\u002Fsecuring-namespaces-using-restrict-authorization-feature-in-chaos-mesh-2e110c3e0fb7)\n- Pavan Kumar: [Chaos Engineering in Kubernetes using Chaos Mesh](https:\u002F\u002Flink.medium.com\u002F1V90dEknugb)\n- Jessica Cherry: [Test your Kubernetes experiments with an open source web interface](https:\u002F\u002Fopensource.com\u002Farticle\u002F21\u002F6\u002Fchaos-mesh-kubernetes)\n- λ.eranga: [Chaos Engineering with Chaos Mesh](https:\u002F\u002Fmedium.com\u002Frahasak\u002Fchaos-engineering-with-chaos-mesh-b040169b51bd)\n- Tomáš Kubica: [Kubernetes prakticky: zlounství s Chaos Mesh a Azure Chaos Studio](https:\u002F\u002Fwww.tomaskubica.cz\u002Fpost\u002F2021\u002Fkubernetes-prakticky-zlounstvi-s-chaos-mesh-a-azure-chaos-studio2\u002F)\n- mend: [Chaos Meshで何ができるのか見てみた](https:\u002F\u002Fqiita.com\u002Fmend\u002Fitems\u002Fdcdfab5e980467bf58e9)\n\n### Community talks\n\n- Twain Taylor: [Chaos Mesh Simplifies & Organizes Chaos Engineering For Kubernetes](https:\u002F\u002Fyoutu.be\u002FshbrjAY86ZQ)\n- Saiyam Pathak\n  - [Let's explore chaos mesh](https:\u002F\u002Fyoutu.be\u002FkMbTYItsTTI)\n  - [Chaos Mesh - Chaos Engineering for Kubernetes](https:\u002F\u002Fyoutu.be\u002FHAU_cjW1bMw)\n  - [Chaos Mesh 2.0](https:\u002F\u002Fyoutu.be\u002FHmQ9cFwxF7g)\n\n## Media coverage\n\n- CodeZine: [オープンソースのカオステストツール「Chaos Mesh 1.0」、一般提供を開始](https:\u002F\u002Fcodezine.jp\u002Farticle\u002Fdetail\u002F12996)\n- @IT atmarkit: [Kubernetes 向けカオスエンジニアリングプラットフォーム「Chaos Mesh 1.0」が公開](https:\u002F\u002Fwww.atmarkit.co.jp\u002Fait\u002Farticles\u002F2010\u002F09\u002Fnews108.html)\n- Publickey: [Kubernetes の Pod やネットワークをわざと落としまくってカオスエンジニアリングのテストができる「Chaos Mesh」がバージョン 1.0 に到達](https:\u002F\u002Fwww.publickey1.jp\u002Fblog\u002F20\u002Fkubernetespodchaos_mesh10.html)\n- InfoQ: [Chaos Engineering on Kubernetes : Chaos Mesh Generally Available with v1.0](https:\u002F\u002Fwww.infoq.com\u002Fnews\u002F2020\u002F10\u002Fkubernetes-chaos-mesh-ga\u002F)\n- TechGenix: [Chaos Mesh Promises to Bring Order to Chaos Engineering](http:\u002F\u002Ftechgenix.com\u002Fchaos-mesh-chaos-engineering\u002F)\n\n## License\n\nChaos Mesh is licensed under the Apache License, Version 2.0. See [LICENSE](.\u002FLICENSE) for the full content.\n\n\u003C!-- markdown-link-check-disable-next-line -->\n[![FOSSA Status](https:\u002F\u002Fapp.fossa.com\u002Fapi\u002Fprojects\u002Fgit%2Bgithub.com%2Fchaos-mesh%2Fchaos-mesh.svg?type=large)](https:\u002F\u002Fapp.fossa.com\u002Fprojects\u002Fgit%2Bgithub.com%2Fchaos-mesh%2Fchaos-mesh?ref=badge_large)\n\n## Trademark\n\nChaos Mesh is a trademark of The Linux Foundation. All rights reserved.\n","Chaos Mesh 是一个面向 Kubernetes 的混沌工程平台，旨在通过模拟各种故障场景来测试和提高系统的稳定性和可靠性。其核心功能包括多种类型的故障注入与强大的故障编排能力，支持在开发、测试乃至生产环境中模拟真实世界可能遇到的问题。技术上，Chaos Mesh 采用 Go 语言开发，并提供了一个直观的 Web 界面，使得设计和监控混沌实验变得简单易行。适用于需要增强系统韧性、进行灾难恢复演练或希望深入了解服务间依赖关系的云原生应用开发团队。","2026-06-11 03:25:19","top_topic"]