Mila Wu
GitHub
parent
73f26e5666
commit
fe8347ef00
|
|
@ -264,6 +264,6 @@ Moving forward, we will continuously improve the Chaos Mesh Dashboard, so that u
|
|||
|
||||
If any of these sound interesting to you, join us in building a world class Chaos Engineering platform. May our applications dance in chaos on Kubernetes!
|
||||
|
||||
If you find a bug or think something is missing, feel free to file an [issue](https://github.com/chaos-mesh/chaos-mesh/issues), open a PR, or message us in the #project-chaos-mesh channel in the [CNCF Slack](https://cloud-native.slack.com/join/shared_invite/zt-lo88vmyc-9e3jSdUXf3dLP2yKql4A0Q#/) workspace.
|
||||
If you find a bug or think something is missing, feel free to file an [issue](https://github.com/chaos-mesh/chaos-mesh/issues), open a PR, or message us in the #project-chaos-mesh channel in the [CNCF Slack](https://slack.cncf.io/) workspace.
|
||||
|
||||
GitHub: [https://github.com/chaos-mesh/chaos-mesh](https://github.com/chaos-mesh/chaos-mesh)
|
||||
|
|
|
|||
|
|
@ -189,6 +189,6 @@ kind delete cluster --name=kind
|
|||
|
||||
Congratulations on your first successful journey into Chaos Engineering. How does it feel? Chaos Engineering is easy, right? But perhaps Chaos Mesh is not that easy-to-use. Command-line operation is inconvenient, writing YAML files manually is a bit tedious, or checking the experiment results is somewhat clumsy? Don't worry, Chaos Dashboard is on its way! Running chaos experiments on the web sure does sound exciting! If you'd like to help us build testing standards for cloud platforms or make Chaos Mesh better, we'd love to hear from you!
|
||||
|
||||
If you find a bug or think something is missing, feel free to file an issue, open a pull request (PR), or join us on the #project-chaos-mesh channel in the [CNCF slack workspace](https://cloud-native.slack.com/join/shared_invite/zt-lo88vmyc-9e3jSdUXf3dLP2yKql4A0Q#/).
|
||||
If you find a bug or think something is missing, feel free to file an issue, open a pull request (PR), or join us on the #project-chaos-mesh channel in the [CNCF slack workspace](https://slack.cncf.io/).
|
||||
|
||||
GitHub: [https://github.com/chaos-mesh/chaos-mesh](https://github.com/chaos-mesh/chaos-mesh)
|
||||
|
|
|
|||
|
|
@ -35,4 +35,4 @@ Currently, Chaos Mesh is in active development for 1.0 GA. Going forward, we wil
|
|||
- Extending chaos injection to application layers
|
||||
- Completing the full chaos engineering loop with status checking, reporting, and scenario defining, etc.
|
||||
|
||||
If you are interested in the project, check out our [website](https://chaos-mesh.org/), join our [Slack](https://cloud-native.slack.com/join/shared_invite/zt-lo88vmyc-9e3jSdUXf3dLP2yKql4A0Q#/) discussions, or attend our [monthly meeting](https://docs.google.com/document/d/1H8IfmhIJiJ1ltg-XLjqR_P_RaMHUGrl1CzvHnKM_9Sc/edit) to know more. Or better yet, become part of us.
|
||||
If you are interested in the project, check out our [website](https://chaos-mesh.org/), join our [Slack](https://slack.cncf.io/) discussions, or attend our [monthly meeting](https://docs.google.com/document/d/1H8IfmhIJiJ1ltg-XLjqR_P_RaMHUGrl1CzvHnKM_9Sc/edit) to know more. Or better yet, become part of us.
|
||||
|
|
|
|||
|
|
@ -144,4 +144,4 @@ This is the complete TiPocket workflow. .
|
|||
|
||||
## Join us
|
||||
|
||||
[Chaos Mesh](https://github.com/pingcap/chaos-mesh) and [TiPocket](https://github.com/pingcap/tipocket) are both in active iterations. We have donated Chaos Mesh donated to [CNCF](https://github.com/cncf/toc/pull/367), and we look forward to more community members joining us in building a complete Chaos Engineering ecosystem. If this sounds interesting to you, check out our [website](https://chaos-mesh.org/), or join #chaos-mesh in [Slack](hthttps://cloud-native.slack.com/join/shared_invite/zt-lo88vmyc-9e3jSdUXf3dLP2yKql4A0Q#/).
|
||||
[Chaos Mesh](https://github.com/pingcap/chaos-mesh) and [TiPocket](https://github.com/pingcap/tipocket) are both in active iterations. We have donated Chaos Mesh donated to [CNCF](https://github.com/cncf/toc/pull/367), and we look forward to more community members joining us in building a complete Chaos Engineering ecosystem. If this sounds interesting to you, check out our [website](https://chaos-mesh.org/), or join #chaos-mesh in [Slack](hthttps://slack.cncf.io/).
|
||||
|
|
|
|||
|
|
@ -43,4 +43,4 @@ How can you participate? It could not be easier with the following steps:
|
|||
|
||||
In the spirit of open source and Hacktoberfest, we welcome all contributions and honor only valid PRs. However, we would not encourage or tolerate spammy contributions, which would not only cause waste to our maintainer’s time but also hurt the feelings and the integrity of the entire open source community. Spammy PRs will be labeled as "invalid" or "spam", and will be closed as invalid.
|
||||
|
||||
Happy hacking! But don’t hack alone. Join #project-chaos-mesh in the [CNCF Slack](https://cloud-native.slack.com/join/shared_invite/zt-lo88vmyc-9e3jSdUXf3dLP2yKql4A0Q#/) to share your experience, provide your feedback on your experience, or let us help with any problem you have.
|
||||
Happy hacking! But don’t hack alone. Join #project-chaos-mesh in the [CNCF Slack](https://slack.cncf.io/) to share your experience, provide your feedback on your experience, or let us help with any problem you have.
|
||||
|
|
|
|||
|
|
@ -66,4 +66,5 @@ In case you want to try Chaos Mesh in your browser, checkout [Katakoda interacti
|
|||
## Join the community
|
||||
|
||||
Anyone who wants to explore the area of chaos engineering or Chaos Mesh are welcomed to join the Chaos Mesh community. Being a member of the Chaos Mesh community, I would like to say it is a lovely community where project maintainers love to engage and hear your views and suggestions for the improvement of the project and the community.
|
||||
To join and learn more about Chaos Mesh, find the #project-chaos-mesh channel in [CNCF slack workspace](https://cloud-native.slack.com/join/shared_invite/zt-lo88vmyc-9e3jSdUXf3dLP2yKql4A0Q#/).
|
||||
|
||||
To join and learn more about Chaos Mesh, find the #project-chaos-mesh channel in [CNCF slack workspace](https://slack.cncf.io/).
|
||||
|
|
|
|||
|
|
@ -66,4 +66,4 @@ However, Chaos Engineering is a big area to work on. In the future, we’d like
|
|||
|
||||
We’ve discussed these features with those who maintain Chaos Mesh, and they said these features are on the Chaos Mesh 2.0 roadmap.
|
||||
|
||||
If you are interested, join the Chaos Mesh community via [Slack](https://cloud-native.slack.com/join/shared_invite/zt-lo88vmyc-9e3jSdUXf3dLP2yKql4A0Q#/) (#project-chaos-mesh) or [GitHub](https://github.com/chaos-mesh/chaos-mesh).
|
||||
If you are interested, join the Chaos Mesh community via [Slack](https://slack.cncf.io/) (#project-chaos-mesh) or [GitHub](https://github.com/chaos-mesh/chaos-mesh).
|
||||
|
|
|
|||
|
|
@ -194,4 +194,4 @@ At present, we have applied chaos-mesh-action to the [TiDB Operator](https://git
|
|||
|
||||
In the future, we plan to apply chaos-mesh-action to more tests to ensure the stability of TiDB and related components. You are welcome to create your own workflow using chaos-mesh-action.
|
||||
|
||||
If you find a bug or think something is missing, feel free to file an issue, open a pull request (PR), or join us on the [#project-chaos-mesh](https://cloud-native.slack.com/join/shared_invite/zt-lo88vmyc-9e3jSdUXf3dLP2yKql4A0Q#/) channel in the [CNCF](https://www.cncf.io/) slack workspace.
|
||||
If you find a bug or think something is missing, feel free to file an issue, open a pull request (PR), or join us on the [#project-chaos-mesh](https://slack.cncf.io/) channel in the [CNCF](https://www.cncf.io/) slack workspace.
|
||||
|
|
|
|||
|
|
@ -134,6 +134,6 @@ I've discussed how we implement fault injection to simulate I/O faults at runtim
|
|||
- ioctl is not supported.
|
||||
- Chaos Mesh does not immediately determine whether a filesystem is successfully mounted. It does so only after one second.
|
||||
|
||||
If you are interested in Chaos Mesh and would like to help us improve it, you're welcome to join [our Slack channel](https://cloud-native.slack.com/join/shared_invite/zt-lo88vmyc-9e3jSdUXf3dLP2yKql4A0Q#/) or submit your pull requests or issues to our [GitHub repository](https://github.com/chaos-mesh/chaos-mesh).
|
||||
If you are interested in Chaos Mesh and would like to help us improve it, you're welcome to join [our Slack channel](https://slack.cncf.io/) or submit your pull requests or issues to our [GitHub repository](https://github.com/chaos-mesh/chaos-mesh).
|
||||
|
||||
This is the first post in a series on Chaos Mesh implementation. If you want to see how other types of fault injection are implemented, stay tuned.
|
||||
|
|
|
|||
|
|
@ -98,4 +98,5 @@ Chaos Mesh 2.0 is now in active development, and it includes community requirem
|
|||
## Last but not least
|
||||
|
||||
Chaos Mesh has grown so much in the past year, yet it is still young, and we have just set sail towards our goal. In the meantime, we call for all of you to participate and help build the Chaos Engineering system ecology together!
|
||||
If you are interested in Chaos Mesh and would like to help us improve it, you're welcome to join [our Slack channel](https://cloud-native.slack.com/join/shared_invite/zt-lo88vmyc-9e3jSdUXf3dLP2yKql4A0Q#/) or submit your pull requests or issues to our [GitHub repository](https://github.com/chaos-mesh/chaos-mesh).
|
||||
|
||||
If you are interested in Chaos Mesh and would like to help us improve it, you're welcome to join [our Slack channel](https://slack.cncf.io/) or submit your pull requests or issues to our [GitHub repository](https://github.com/chaos-mesh/chaos-mesh).
|
||||
|
|
|
|||
|
|
@ -55,7 +55,7 @@ Execute `kubectl describe` to check the specified chaos experiment resource.
|
|||
kubectl get pods -n yourNamespace --show-labels
|
||||
```
|
||||
|
||||
If the above steps cannot solve the problem or you encounter other related errors in controller's log, [file an issue](https://github.com/chaos-mesh/chaos-mesh/issues) or message us in the #project-chaos-mesh channel in the [CNCF Slack](https://cloud-native.slack.com/join/shared_invite/zt-lo88vmyc-9e3jSdUXf3dLP2yKql4A0Q#/) workspace.
|
||||
If the above steps cannot solve the problem or you encounter other related errors in controller's log, [file an issue](https://github.com/chaos-mesh/chaos-mesh/issues) or message us in the #project-chaos-mesh channel in the [CNCF Slack](https://slack.cncf.io/) workspace.
|
||||
|
||||
## IOChaos
|
||||
|
||||
|
|
|
|||
|
|
@ -66,7 +66,7 @@ module.exports = {
|
|||
},
|
||||
{
|
||||
label: 'Slack (#project-chaos-mesh)',
|
||||
href: 'https://cloud-native.slack.com/join/shared_invite/zt-lo88vmyc-9e3jSdUXf3dLP2yKql4A0Q#/',
|
||||
href: 'https://slack.cncf.io/',
|
||||
},
|
||||
],
|
||||
},
|
||||
|
|
|
|||
|
|
@ -55,7 +55,7 @@ Execute `kubectl describe` to check the specified chaos experiment resource.
|
|||
kubectl get pods -n yourNamespace --show-labels
|
||||
```
|
||||
|
||||
If the above steps cannot solve the problem or you encounter other related errors in controller's log, [file an issue](https://github.com/chaos-mesh/chaos-mesh/issues) or message us in the #project-chaos-mesh channel in the [CNCF Slack](https://cloud-native.slack.com/join/shared_invite/zt-lo88vmyc-9e3jSdUXf3dLP2yKql4A0Q#/) workspace.
|
||||
If the above steps cannot solve the problem or you encounter other related errors in controller's log, [file an issue](https://github.com/chaos-mesh/chaos-mesh/issues) or message us in the #project-chaos-mesh channel in the [CNCF Slack](https://slack.cncf.io/) workspace.
|
||||
|
||||
## IOChaos
|
||||
|
||||
|
|
|
|||
|
|
@ -55,7 +55,7 @@ Execute `kubectl describe` to check the specified chaos experiment resource.
|
|||
kubectl get pods -n yourNamespace --show-labels
|
||||
```
|
||||
|
||||
If the above steps cannot solve the problem or you encounter other related errors in controller's log, [file an issue](https://github.com/chaos-mesh/chaos-mesh/issues) or message us in the #project-chaos-mesh channel in the [CNCF Slack](https://cloud-native.slack.com/join/shared_invite/zt-lo88vmyc-9e3jSdUXf3dLP2yKql4A0Q#/) workspace.
|
||||
If the above steps cannot solve the problem or you encounter other related errors in controller's log, [file an issue](https://github.com/chaos-mesh/chaos-mesh/issues) or message us in the #project-chaos-mesh channel in the [CNCF Slack](https://slack.cncf.io/) workspace.
|
||||
|
||||
## IOChaos
|
||||
|
||||
|
|
|
|||
|
|
@ -55,7 +55,7 @@ Execute `kubectl describe` to check the specified chaos experiment resource.
|
|||
kubectl get pods -n yourNamespace --show-labels
|
||||
```
|
||||
|
||||
If the above steps cannot solve the problem or you encounter other related errors in controller's log, [file an issue](https://github.com/chaos-mesh/chaos-mesh/issues) or message us in the #project-chaos-mesh channel in the [CNCF Slack](https://cloud-native.slack.com/join/shared_invite/zt-lo88vmyc-9e3jSdUXf3dLP2yKql4A0Q#/) workspace.
|
||||
If the above steps cannot solve the problem or you encounter other related errors in controller's log, [file an issue](https://github.com/chaos-mesh/chaos-mesh/issues) or message us in the #project-chaos-mesh channel in the [CNCF Slack](https://slack.cncf.io/) workspace.
|
||||
|
||||
## IOChaos
|
||||
|
||||
|
|
|
|||
Loading…
Reference in New Issue