Issue Description

Type: feature request

Describe what happened (or what feature you want)

chaosblade是一款覆盖面很广的故障注入测试工具，因此我希望引入此软件对 K8s Paas平台进行测试，但是发现只能针对特定的pod进行故障注入（delete pod或者pod cpu负载等），没有其他针对Paas 的chaos工具（Powerfulseal、Chaos-mesh等）拥有在规定时间内随机等delete 规定分区下的po

There is no e2e test and documents for external network delay and partition now 🤦 .

The e2e test could be found in /test/e2e/chaos/basic.go. Reading other tests in that file could help accomplish this issue.

Example for extern network delay:

apiVersion: chaos-mesh.org/v1alpha1
kind: NetworkChaos
metadata:
  name: network-netem-example
  namespace: chaos-testing
spec:

Running 2.9.1 (yes, I know, it's old). We have several different clusters, but don't have the same k8s deployments in each cluster. Tried to use a generic policy definition. When it is applied in a cluster which doesn't have one of the deployments, seal doesn't handle the 404 from k8s and dies. Yes, we can change the policies, but also seal shouldn't die in this scenario.

While this was wit

This issue is

Currently this will work:

"method": [
        {
            "name": "send-invalid-request",
            "type": "action",
            "provider": {
                "type": "process",
                "path": "echo",
                "arguments": "${request_file}"
            }
        }
    ]

But this won't:

"method": [
        {
            "name": "send-invalid-

I would like to drop Spring Boot support for 1.5.x. It is EOL https://spring.io/blog/2018/07/30/spring-boot-1-x-eol-aug-1st-2019
I would also add some notes in the docs, that we adhere to the spring boot lifecycle in order to be transparent about dropping support for versions.

At the moment the number of tasks able to be launched for a given scenario is 10 do to restriction with ECS. A workaround that creates multiple ECS instances for a given scenario based on the number of tasks requested should be added.