From bbd5473ba5eaa2f521eda5c0b969f68d0cccdd19 Mon Sep 17 00:00:00 2001 From: Yue Yang Date: Mon, 9 Oct 2023 11:16:20 +0800 Subject: [PATCH] fix: links Signed-off-by: Yue Yang --- ...os-mesh-remake-one-step-closer-toward-chaos-as-a-service.md | 2 +- mlc_config.json | 3 +++ 2 files changed, 4 insertions(+), 1 deletion(-) diff --git a/blog/2021-06-25-chaos-mesh-remake-one-step-closer-toward-chaos-as-a-service.md b/blog/2021-06-25-chaos-mesh-remake-one-step-closer-toward-chaos-as-a-service.md index bd010ab..85fcca5 100644 --- a/blog/2021-06-25-chaos-mesh-remake-one-step-closer-toward-chaos-as-a-service.md +++ b/blog/2021-06-25-chaos-mesh-remake-one-step-closer-toward-chaos-as-a-service.md @@ -142,7 +142,7 @@ To enable full plugin support, we need to explore a new method to add plugins. A For real-world systems, a single Chaos Engineering tool can hardly exhaust all possible use cases. That's why integrating with other chaos tools can make the Chaos Engineering ecosystem more powerful. -There are numerous Chaos Engineering tools on the market. Litmus's [Kubernetes implementation](https://github.com/litmuschaos/litmus-go/tree/master/chaoslib/powerfulseal) is based on [PowerfulSeal](https://github.com/powerfulseal/powerfulseal), while its [container implementation](https://github.com/litmuschaos/litmus-go/tree/master/chaoslib/pumba) is based on [Pumba](https://github.com/alexei-led/pumba). [Kraken](https://github.com/cloud-bulldozer/kraken) focuses on Kubernetes, [AWSSSMChaosRunner](https://github.com/amzn/awsssmchaosrunner) focuses on AWS, and [Toxiproxy](https://github.com/shopify/toxiproxy) targets TCP. There are also merging projects based on [Envoy](https://docs.google.com/presentation/d/1gMlmXqH6ufnb8eNO10WqVjqrPRGAO5-1S1zjcGo1Zr4/edit#slide=id.g58453c664c_2_75) and Istio. +There are numerous Chaos Engineering tools on the market. Litmus's [Kubernetes implementation](https://github.com/litmuschaos/litmus-go/tree/2.14.1/chaoslib/powerfulseal) is based on [PowerfulSeal](https://github.com/powerfulseal/powerfulseal), while its [container implementation](https://github.com/litmuschaos/litmus-go/tree/2.14.1/chaoslib/pumba) is based on [Pumba](https://github.com/alexei-led/pumba). [Kraken](https://github.com/cloud-bulldozer/kraken) focuses on Kubernetes, [AWSSSMChaosRunner](https://github.com/amzn/awsssmchaosrunner) focuses on AWS, and [Toxiproxy](https://github.com/shopify/toxiproxy) targets TCP. There are also merging projects based on [Envoy](https://docs.google.com/presentation/d/1gMlmXqH6ufnb8eNO10WqVjqrPRGAO5-1S1zjcGo1Zr4/edit#slide=id.g58453c664c_2_75) and Istio. To manage the various chaos tools, we may need a uniform pattern, such as [Chaos Hub](https://hub.litmuschaos.io/). diff --git a/mlc_config.json b/mlc_config.json index c7f8417..0f19b94 100644 --- a/mlc_config.json +++ b/mlc_config.json @@ -8,6 +8,9 @@ }, { "pattern": "^http://localhost" + }, + { + "pattern": "^https://twitter.com" } ], "aliveStatusCodes": [200, 403, 500, 502, 503]