user avatar
[BugBash] SC2164: Fix cd fails case issue in bootstrap.sh (#3236)
Anurag Paliwal authored
* SC2164: Fix in case cd fails issue in bootstrap.sh
Signed-off-by: default avatarAnurag Paliwal <anuragpaliwal@gmail.com>

* chore: remove useless cd
Signed-off-by: default avatarYue Yang <g1enyy0ung@gmail.com>
Signed-off-by: default avatarAnurag Paliwal <anuragpaliwal@gmail.com>
Signed-off-by: default avatarYue Yang <g1enyy0ung@gmail.com>
Co-authored-by: default avatarYue Yang <g1enyy0ung@gmail.com>
42fcabc1
Name Last commit Last update
.github chore: update PR template due to v2.3 released (#3534)
api fix: Omit optional fields explicitly (#3531)
build timechaos: support injection on aarch64 (#3088)
ci chaos-daemon support graceful shutdown (#2668)
cmd feat: update API requests with OpenAPI generated client (#2926)
config Sync latest Chaosd and PhysicalMachineChaos (#3477)
controllers Sync latest Chaosd and PhysicalMachineChaos (#3477)
e2e-test feat: update API requests with OpenAPI generated client (#2926)
examples [multicluster] bootstrap controller manager at runtime with clusterregistry (#3342)
hack feat: update API requests with OpenAPI generated client (#2926)
helm/chaos-mesh Sync latest Chaosd and PhysicalMachineChaos (#3477)
images feat: update API requests with OpenAPI generated client (#2926)
manifests Sync latest Chaosd and PhysicalMachineChaos (#3477)
pkg Use `net.Interfaces()` to implement `getAllInterfaces()` (#3484)
static README: update chaos mesh architecture image (#2596)
test renamed all occurances of chaos testing to chaos-mesh (#3353)
tools refactor: move from io/ioutil to io and os packages (#3076)
ui [BugBash] SC2164: Fix cd fails case issue in bootstrap.sh (#3236)
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 feat: next `New Workflow` in UI (#3185)
.muse.toml upgrade to apiextensions.k8s.io/v1 CRD (#1896)
ADOPTERS.md Add Maycur as Adopter (#3052)
CHANGELOG.md
CODE_OF_CONDUCT.md
CONTRIBUTING.md
GOVERNANCE.md
LICENSE
MAINTAINERS.md
Makefile
PROJECT
README.md
ROADMAP.md
SECURITY.md
codecov.yml
env-images.yaml
go.mod
go.sum
install.sh
revive.toml
tools.go
tools.json
Chaos Mesh Logo

Upload Image codecov LICENSE Language Go Report Card GoDoc FOSSA Status CII Best Practices

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.