Skip to content
This repository was archived by the owner on Jan 28, 2022. It is now read-only.

Commit e80ca9c

Browse files
upload-chaos-mesh-q&a (chaos-mesh#79)
* upload-q&a-post Signed-off-by: Mila Wu <[email protected]> * upload-q&a-post Signed-off-by: Mila Wu <[email protected]> * upload-q&a-post Signed-off-by: Mila Wu <[email protected]> * upload-q&a-post Signed-off-by: Mila Wu <[email protected]>
1 parent 33bccd4 commit e80ca9c

6 files changed

+69
-4
lines changed

blog/2021-06-20-lfx-mentorship-enriching-awschaos.md

Lines changed: 0 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -10,7 +10,6 @@ tags: [Chaos Mesh, Chaos Engineering, LFX Mentorship, AWS Chaos]
1010
---
1111
![LFX Mentorship Experience](/img/mentorship_blog.jpeg)
1212

13-
## About Me
1413

1514
[I’m](https://mentorship.lfx.linuxfoundation.org/mentee/6a0bf7de-9e18-4acb-9a66-f5fecdbeb42e) a junior undergraduate majoring in Biomedical Engineering in the Department of Biotechnology and Medical Engineering at the [National Institute of Technology Rourkela](https://nitrkl.ac.in/), India. For someone who started to code only because I was fascinated by it, it was all a journey of self-learning, filled with various adversities. But when I started with open-source contributions, it was all very beginner-friendly and I came across a lot of people who helped me learn the tech stack better.
1615

File renamed without changes.

blog/2021-07-07-restrict-authorization.md

Lines changed: 4 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -11,13 +11,14 @@ tags: [Chaos Mesh, Chaos Engineering]
1111

1212
![Chaos engineering tools](/img/chaos-mesh-restrict-authorization.jpeg)
1313

14-
# Cluster multi-tenancy
15-
1614
A [multi-tenant](https://cloud.google.com/kubernetes-engine/docs/concepts/multitenancy-overview) cluster is shared by multiple users and/or workloads which are referred to as "tenants".The operators of multi-tenant clusters must isolate tenants from each other to minimize the damage that a compromised or malicious tenant can do to the cluster and other tenants.
17-
When you plan a multi-tenant architecture, you should consider the layers of resource isolation in Kubernetes: cluster, namespace, node, Pod, and container.
1815

1916
<!--truncate-->
2017

18+
# Cluster multi-tenancy
19+
20+
When you plan a multi-tenant architecture, you should consider the layers of resource isolation in Kubernetes: cluster, namespace, node, Pod, and container.
21+
2122
Although Kubernetes cannot guarantee perfectly secure isolation between tenants, it does offer features that may be sufficient for specific use cases. You can separate each tenant and their Kubernetes resources into their own [namespaces](https://kubernetes.io/docs/concepts/overview/working-with-objects/namespaces/).
2223
Kubernetes supports multiple virtual clusters backed by the same physical cluster. These virtual clusters are called namespaces. [Namespaces](https://kubernetes.io/docs/concepts/overview/working-with-objects/namespaces/) are intended for use in environments with many users spread across multiple teams, or projects.
2324

blog/2021-07-09-chaos-mesh-q&a.md

Lines changed: 65 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,65 @@
1+
---
2+
slug: /chaos-mesh-q&a
3+
title: 'Chaos Mesh® Q&A'
4+
author: Chaos Mesh Community
5+
author_url: https://github.com/chaos-mesh
6+
author_image_url: https://avatars1.githubusercontent.com/u/59082378?v=4
7+
image: /img/chaos-mesh-q&a.jpeg
8+
tags: [Chaos Mesh, Chaos Engineering]
9+
---
10+
11+
![Chaos Mesh Q&A](/img/chaos-mesh-q&a.jpeg)
12+
13+
At KubeCon EU 2021, the [Chaos Mesh](https://chaos-mesh.org/) team hosted two “office hours sessions” where newcomers, community members, and project maintainers had a chance to chat, get to know each other, and learn more about the project.
14+
15+
<!--truncate-->
16+
17+
Big thanks to the more than 200 of you who joined us! We received so many great questions during the session, we thought we’d do a round up Q&A.
18+
19+
20+
## Your questions answered
21+
22+
**Q: Is Chaos Mesh compatible with Service Meshes, such as Istio?**
23+
24+
**A:** Yes, you can use Chaos Mesh in the Service Mesh environment. At one of our [previous community meetings](https://www.youtube.com/watch?v=paIgJYOhdGw), Sergio Méndez and Jossie Castrillo from the University of San Carlos of Guatemala shared how they used Linkerd and Chaos Mesh to conduct chaos experiments for their project, “[COVID-19 Realtime Vaccinated People Visualizer](https://github.com/sergioarmgpl/operating-systems-usac-course/blob/master/lang/en/projects/project1v3/project1.md)”.
25+
26+
![Project Architecture](/img/chaos-mesh-linkerd-architecture.png)
27+
28+
<div class="caption-center"> Project Architecture </div>
29+
30+
<br/>
31+
32+
**Q: Can I use Chaos Mesh on-premises or do I need Amazon Web Services (AWS) or Google Cloud Platform (GCP)?**
33+
34+
**A:** You can do either! You can deploy Chaos Mesh on your Kubernetes cluster, so it does not matter whether you manage it yourself or have it hosted on AWS or GCP. However, if you would like to use it in a Kubernetes environment, you need to [set relevant parameters](https://chaos-mesh.org/docs/user_guides/installation) during installation.
35+
36+
**Q: How do "chaos actions" work?**
37+
38+
**A:** Chaos Mesh uses Kubernetes CustomResourceDefinitions (CRDs) to manage chaos experiments. Different fault injection behaviors are implemented in different ways, but the overall idea is the same: Chaos Mesh uses an application's execution link to inject chaos into the application. For example, when we inject chaos into the overall link of network interaction, the network interaction card is passed through. Because Linux uses traffic control to increase interference to the specific network interaction card, we can directly use traffic control for network fault injection.
39+
40+
**Q: Are you going to add probe support to Chaos Mesh for steady state detection and experiment validation?**
41+
42+
**A:** Currently, there is no plan to add this support. Steady state detection and experiment validation are necessary if an application is ready for production. Chaos Mesh itself does not monitor related work, but provides an interface to access existing monitoring systems or the status interface of the application to monitor and detect the application’s steady state.
43+
44+
**Q: What elevated privileges do the Chaos Mesh pods need?**
45+
46+
**A:** By default, the Chaos Daemon components in Chaos Mesh run in the `privileged` mode. If your Kubernetes cluster version is v3.11 or higher, you can replace `privileged` mode by configuring `capabilities`.
47+
48+
**Q: Can I implement Chaos Mesh inside build pipelines to log specific test results?**
49+
50+
**A:** Yes, that’s easy to do. You can integrate Chaos Mesh with pipeline systems such as Argo, Jenkins, GitHub Action, and Spanner. Chaos Mesh uses Kubernetes CRDs to manage chaos experiments. To inject chaos, you only need to create the chaos CRD object you want in the pipeline. You can obtain the running status of an experiment through its status structure and event.
51+
52+
**Q: What can we expect from the 2.0 release? Can you share some updates on HTTPChaos?**
53+
54+
**A:** Chaos Mesh 2.0 will provide native workflow support, and users can arrange chaos experiments in Chaos Mesh. In addition, for Chaos Mesh 2.0, we have reconstructed the existing chaos controller so that users can more easily add new fault injection types. As for HTTPChaos, we’re adding network failure simulation to the HTTP application layer!
55+
56+
57+
## Join the Chaos Mesh community
58+
59+
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).
60+
61+
62+
63+
64+
65+
_Jenkins® is a registered trademark of LF Charities Inc._
428 KB
Loading

static/img/chaos-mesh-q&a.jpeg

122 KB
Loading

0 commit comments

Comments
 (0)