Skip to content
GitLab
"git@git.gitsec.cn:baidan/Chaos-Mesh.git" did not exist on "a67a7093da9686d9b505bd3f6b74d0b1b1bc889a"
Switch branch/tag
History Find file
Clone
user avatar
Change from DOCKER_REGISTRY to IMAGE_REGISTRY in some scripts (#2757)
YangKeao authored 
* modify DOCKER_REGISTRY in make script
Signed-off-by: default avatarYangKeao <yangkeao@chunibyo.icu>

* align the help message
Signed-off-by: default avatarYangKeao <yangkeao@chunibyo.icu>
Co-authored-by: default avatarYue Yang <g1enyy0ung@gmail.com>
Co-authored-by: default avatarTi Chi Robot <ti-community-prow-bot@tidb.io>
a67a7093
Name Last commit Last update
.github Change from DOCKER_REGISTRY to IMAGE_REGISTRY in some scripts (#2757)
api fix document for container selector (#2755)
build build: fix environment variables in build scripts (#2771)
ci e2e: dynamically get branch name from env (#2702)
cmd add physical machine crd (#2587)
config fix document for container selector (#2755)
controllers refactor: rename, documents and tests for action.Delegate (#2663)
e2e-test chore(deps): Bump github.com/containerd/containerd from 1.5.4 to 1.5.8 (#2745)
examples JVMChaos: refine with byteman (#2366)
hack Change from DOCKER_REGISTRY to IMAGE_REGISTRY in some scripts (#2757)
helm/chaos-mesh fix document for container selector (#2755)
images Change from DOCKER_REGISTRY to IMAGE_REGISTRY in some scripts (#2757)
manifests fix document for container selector (#2755)
pkg fix document for container selector (#2755)
static README: update chaos mesh architecture image (#2596)
test add physical machine crd (#2587)
tools feat!: UI monorepo (#2590)
ui fix document for container selector (#2755)
workflow/docs workflow basic CRD and reconcilers (#1551)
.dockerignore upgrade grpc to remove warning (#1757)
.editorconfig style: add .editorconfig for *.go (#821)
.gitignore add several build script to replace template (#2640)
.lift.toml add Sonatype Lift configurtion file (#2373)
.muse.toml upgrade to apiextensions.k8s.io/v1 CRD (#1896)
ADOPTERS.md Add new adopter (#2765)
CODE_OF_CONDUCT.md
CONTRIBUTING.md
GOVERNANCE.md
LICENSE
MAINTAINERS.md
Makefile
PROJECT
README.md
ROADMAP.md
SECURITY.md
codecov.yml
go.mod
go.sum
install.sh
revive.toml
tools.go
tools.json
README.md
Chaos Mesh Logo

Upload Image codecov LICENSE Language Go Report Card GoDoc FOSSA Status

Note:

This readme and related documentation are Work in Progress.

Chaos Mesh is a Cloud Native Computing Foundation (CNCF) hosted project. It is a cloud-native Chaos Engineering platform that orchestrates chaos on Kubernetes environments. At the current stage, it has the following components:

  • Chaos Operator: the core component for chaos orchestration. Fully open sourced.
  • Chaos Dashboard: a Web UI for managing, designing, monitoring Chaos Experiments.

See the following demo video for a quick view of Chaos Mesh:

Watch the video

Chaos Operator

Chaos 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 three components at play:

Controller-manager: used to schedule and manage the lifecycle of CRD objects.

Chaos-daemon: runs as daemonset with privileged system permissions over network, Cgroup, etc. for a specific node.

Chaos Operator

Chaos Operator uses CustomResourceDefinition (CRD) to define chaos objects. The current implementation supports a few types of CRD objects for fault injection, namely DNSChaos, PodChaos, PodIOChaos, PodNetworkChaos, NetworkChaos, IOChaos, TimeChaos, StressChaos, and KernelChaos, which correspond to the following major actions (experiments):

  • pod-kill: The selected pod is killed (ReplicaSet or something similar may be needed to ensure the pod will be restarted).
  • pod-failure: The selected pod will be unavailable in a specified period of time.
  • container-kill: The selected container is killed in the selected pod.
  • netem chaos: Network chaos such as delay, duplication, etc.
  • network-partition: Simulate network partition.
  • IO chaos: Simulate file system faults such as I/O delay, read/write errors, etc.
  • time chaos: The selected pod will be injected with clock skew.
  • cpu-burn: Simulate the CPU of the selected pod stress.
  • memory-burn: Simulate the memory of the selected pod stress.
  • kernel chaos: The selected pod will be injected with (slab, bio, etc) errors.
  • dns chaos: The selected pod will be injected with dns errors, such as error, random.

Quick start

See Chaos Mesh Docs.

Adopters

See ADOPTERS.

Blogs

Blogs on Chaos Mesh design & implementation, features, chaos engineering, community updates, etc. See Chaos Mesh Blogs. Here are some recommended ones for you to start with:

Contributing

See the contributing guide and development guide.

Community

Please reach out for bugs, feature requests, and other issues via:

  • Following us on Twitter @chaos_mesh.

  • Joining the #project-chaos-mesh channel in the CNCF Slack workspace.

  • Filing an issue or opening a PR against this repository.

Community meeting

On the fourth Thursday of every month (unless otherwise specified), the Chaos Mesh community holds a monthly meeting by video conference to discuss the status of Chaos Mesh.

Quick links:

Community blogs

Community talks

Media coverage

FAQs

See FAQs.

Roadmap

See ROADMAP.

License

Chaos Mesh is licensed under the Apache License, Version 2.0. See LICENSE for the full license text.

FOSSA Status

Trademark

Chaos Mesh is a trademark of The Linux Foundation. All rights reserved.

免费DevSecOps平台，让您的项目体验完整的DevSecOps流程，让项目更安全