-
Notifications
You must be signed in to change notification settings - Fork 614
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
feat: new project idea for Chaos Mesh
Signed-off-by: STRRL <[email protected]>
- Loading branch information
Showing
1 changed file
with
12 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -89,3 +89,15 @@ | |
- Pierangelo Di Pilato (@pierdipi, [email protected]) | ||
- Upstream Issue: https://github.com/knative/eventing/issues/7530 | ||
|
||
### Chaos Mesh | ||
|
||
#### Observability for StressChaos | ||
|
||
- Description: StressChaos is a chaos experiment that injects stress to the system. The current implementation of StressChaos is lack of observability, most of observability solutions could not observe the stress at Pod level, but only at Node level. This project is to enhance observability for StressChaos. | ||
- Expected Outcome: Chaos Mesh end users could observe the injected stress at Pod level. | ||
- Recommended Skills: Golang, Kubernetes, Linux, Observability Tools(e.g. Prometheus, Grafana, etc.) | ||
- Mentor(s): | ||
- Zhiqiang Zhou(@STRRL, [email protected]) | ||
- Yue Yang(@g1eny0ung, [email protected]) | ||
- Cwen Yin(@cwen0, [email protected]) | ||
- Upstream Issue: https://github.com/chaos-mesh/chaos-mesh/discussions/3012, https://github.com/chaos-mesh/chaos-mesh/issues/3651 |