diff --git a/demo/sample-applications/sock-shop/README.md b/demo/sample-applications/sock-shop/README.md index e1a951b980f..427f5589ecd 100644 --- a/demo/sample-applications/sock-shop/README.md +++ b/demo/sample-applications/sock-shop/README.md @@ -44,7 +44,7 @@ Chaos experiments on sock-shop app with grafana dashboard to monitor it. - Install the chaos experiments in admin(litmus) namespace ``` - kubectl apply -f https://hub.litmuschaos.io/api/chaos/1.6.1?file=charts/generic/experiments.yaml -n litmus + kubectl apply -f https://hub.litmuschaos.io/api/chaos/1.6.1?file=faults/generic/experiments.yaml -n litmus ``` - Install the chaos experiment metrics exporter and chaos event exporter diff --git a/mkdocs/docs/experiments/categories/aws-ssm/aws-ssm-chaos-by-id.md b/mkdocs/docs/experiments/categories/aws-ssm/aws-ssm-chaos-by-id.md index 1cfc0d1f0f9..50d440f81f6 100644 --- a/mkdocs/docs/experiments/categories/aws-ssm/aws-ssm-chaos-by-id.md +++ b/mkdocs/docs/experiments/categories/aws-ssm/aws-ssm-chaos-by-id.md @@ -18,7 +18,7 @@ ??? info "Verify the prerequisites" - Ensure that Kubernetes Version > 1.16 - Ensure that the Litmus Chaos Operator is running by executing kubectl get pods in operator namespace (typically, litmus).If not, install from here - - Ensure that the aws-ssm-chaos-by-id experiment resource is available in the cluster by executing kubectl get chaosexperiments in the desired namespace. If not, install from here + - Ensure that the aws-ssm-chaos-by-id experiment resource is available in the cluster by executing kubectl get chaosexperiments in the desired namespace. If not, install from here - Ensure that you have the required AWS access and your target EC2 instances have attached an IAM instance profile. To know more checkout [Systems Manager Docs](https://docs.aws.amazon.com/systems-manager/latest/userguide/setup-launch-managed-instance.html). - Ensure to create a Kubernetes secret having the AWS access configuration(key) in the `CHAOS_NAMESPACE`. A sample secret file looks like: @@ -50,7 +50,6 @@ ??? note "View the Minimal RBAC permissions" - [embedmd]:# (https://raw.githubusercontent.com/litmuschaos/chaos-charts/master/charts/aws-ssm/aws-ssm-chaos-by-id/rbac.yaml yaml) ```yaml --- apiVersion: v1 diff --git a/mkdocs/docs/experiments/categories/aws-ssm/aws-ssm-chaos-by-tag.md b/mkdocs/docs/experiments/categories/aws-ssm/aws-ssm-chaos-by-tag.md index 3b4747db49c..931ebe8129e 100644 --- a/mkdocs/docs/experiments/categories/aws-ssm/aws-ssm-chaos-by-tag.md +++ b/mkdocs/docs/experiments/categories/aws-ssm/aws-ssm-chaos-by-tag.md @@ -18,7 +18,7 @@ ??? info "Verify the prerequisites" - Ensure that Kubernetes Version > 1.16 - Ensure that the Litmus Chaos Operator is running by executing kubectl get pods in operator namespace (typically, litmus).If not, install from here - - Ensure that the aws-ssm-chaos-by-tag experiment resource is available in the cluster by executing kubectl get chaosexperiments in the desired namespace. If not, install from here + - Ensure that the aws-ssm-chaos-by-tag experiment resource is available in the cluster by executing kubectl get chaosexperiments in the desired namespace. If not, install from here - Ensure that you have the required AWS access and your target EC2 instances have attached an IAM instance profile. To know more checkout [Systems Manager Docs](https://docs.aws.amazon.com/systems-manager/latest/userguide/setup-launch-managed-instance.html). - Ensure to create a Kubernetes secret having the AWS access configuration(key) in the `CHAOS_NAMESPACE`. A sample secret file looks like: @@ -50,7 +50,6 @@ ??? note "View the Minimal RBAC permissions" - [embedmd]:# (https://raw.githubusercontent.com/litmuschaos/chaos-charts/master/charts/aws-ssm/aws-ssm-chaos-by-tag/rbac.yaml yaml) ```yaml --- apiVersion: v1 diff --git a/mkdocs/docs/experiments/categories/aws/ebs-loss-by-id.md b/mkdocs/docs/experiments/categories/aws/ebs-loss-by-id.md index e9fe69bc891..3a7dfa34cf2 100644 --- a/mkdocs/docs/experiments/categories/aws/ebs-loss-by-id.md +++ b/mkdocs/docs/experiments/categories/aws/ebs-loss-by-id.md @@ -17,7 +17,7 @@ Tests deployment sanity (replica availability & uninterrupted service) and recov ??? info "Verify the prerequisites" - Ensure that Kubernetes Version > 1.16 - Ensure that the Litmus Chaos Operator is running by executing kubectl get pods in operator namespace (typically, litmus).If not, install from here - - Ensure that the ebs-loss-by-id experiment resource is available in the cluster by executing kubectl get chaosexperiments in the desired namespace. If not, install from here + - Ensure that the ebs-loss-by-id experiment resource is available in the cluster by executing kubectl get chaosexperiments in the desired namespace. If not, install from here - Ensure that you have sufficient AWS access to attach or detach an ebs volume for the instance. - Ensure to create a Kubernetes secret having the AWS access configuration(key) in the `CHAOS_NAMESPACE`. A sample secret file looks like: @@ -49,7 +49,6 @@ Tests deployment sanity (replica availability & uninterrupted service) and recov ??? note "View the Minimal RBAC permissions" - [embedmd]:# (https://raw.githubusercontent.com/litmuschaos/chaos-charts/master/charts/kube-aws/ebs-loss-by-id/rbac.yaml yaml) ```yaml --- apiVersion: v1 diff --git a/mkdocs/docs/experiments/categories/aws/ebs-loss-by-tag.md b/mkdocs/docs/experiments/categories/aws/ebs-loss-by-tag.md index 62d0269735d..33d2fda07c3 100644 --- a/mkdocs/docs/experiments/categories/aws/ebs-loss-by-tag.md +++ b/mkdocs/docs/experiments/categories/aws/ebs-loss-by-tag.md @@ -17,7 +17,7 @@ Tests deployment sanity (replica availability & uninterrupted service) and recov ??? info "Verify the prerequisites" - Ensure that Kubernetes Version > 1.16 - Ensure that the Litmus Chaos Operator is running by executing kubectl get pods in operator namespace (typically, litmus).If not, install from here - - Ensure that the ebs-loss-by-tag experiment resource is available in the cluster by executing kubectl get chaosexperiments in the desired namespace. If not, install from here + - Ensure that the ebs-loss-by-tag experiment resource is available in the cluster by executing kubectl get chaosexperiments in the desired namespace. If not, install from here - Ensure that you have sufficient AWS access to attach or detach an ebs volume for the instance. - Ensure to create a Kubernetes secret having the AWS access configuration(key) in the `CHAOS_NAMESPACE`. A sample secret file looks like: @@ -49,7 +49,6 @@ Tests deployment sanity (replica availability & uninterrupted service) and recov ??? note "View the Minimal RBAC permissions" - [embedmd]:# (https://raw.githubusercontent.com/litmuschaos/chaos-charts/master/charts/kube-aws/ebs-loss-by-tag/rbac.yaml yaml) ```yaml --- apiVersion: v1 diff --git a/mkdocs/docs/experiments/categories/aws/ec2-terminate-by-id.md b/mkdocs/docs/experiments/categories/aws/ec2-stop-by-id.md similarity index 84% rename from mkdocs/docs/experiments/categories/aws/ec2-terminate-by-id.md rename to mkdocs/docs/experiments/categories/aws/ec2-stop-by-id.md index 5dcdcaa1b4e..ffe81cec08c 100644 --- a/mkdocs/docs/experiments/categories/aws/ec2-terminate-by-id.md +++ b/mkdocs/docs/experiments/categories/aws/ec2-stop-by-id.md @@ -1,11 +1,11 @@ ## Introduction -- It causes termination of an EC2 instance by instance ID or list of instance IDs before bringing it back to running state after the specified chaos duration. +- It causes stopping of an EC2 instance by instance ID or list of instance IDs before bringing it back to running state after the specified chaos duration. - It helps to check the performance of the application/process running on the ec2 instance. When the MANAGED_NODEGROUP is enable then the experiment will not try to start the instance post chaos instead it will check of the addition of the new node instance to the cluster. -!!! tip "Scenario: Terminate EC2 Instance" - ![EC2 Terminate By ID](../../images/ec2-terminate.png) +!!! tip "Scenario: Stop EC2 Instance" + ![EC2 Stop By ID](../../images/ec2-stop.png) ## Uses @@ -17,7 +17,7 @@ When the MANAGED_NODEGROUP is enable then the experiment will not try to start t ??? info "Verify the prerequisites" - Ensure that Kubernetes Version > 1.16 - Ensure that the Litmus Chaos Operator is running by executing kubectl get pods in operator namespace (typically, litmus).If not, install from here - - Ensure that the ec2-terminate-by-id experiment resource is available in the cluster by executing kubectl get chaosexperiments in the desired namespace. If not, install from here + - Ensure that the ec2-stop-by-id experiment resource is available in the cluster by executing kubectl get chaosexperiments in the desired namespace. If not, install from here - Ensure that you have sufficient AWS access to stop and start an ec2 instance. - Ensure to create a Kubernetes secret having the AWS access configuration(key) in the `CHAOS_NAMESPACE`. A sample secret file looks like: @@ -54,24 +54,23 @@ When the MANAGED_NODEGROUP is enable then the experiment will not try to start t ??? note "View the Minimal RBAC permissions" - [embedmd]:# (https://raw.githubusercontent.com/litmuschaos/chaos-charts/master/charts/kube-aws/ec2-terminate-by-id/rbac.yaml yaml) ```yaml --- apiVersion: v1 kind: ServiceAccount metadata: - name: ec2-terminate-by-id-sa + name: ec2-stop-by-id-sa namespace: default labels: - name: ec2-terminate-by-id-sa + name: ec2-stop-by-id-sa app.kubernetes.io/part-of: litmus --- apiVersion: rbac.authorization.k8s.io/v1 kind: ClusterRole metadata: - name: ec2-terminate-by-id-sa + name: ec2-stop-by-id-sa labels: - name: ec2-terminate-by-id-sa + name: ec2-stop-by-id-sa app.kubernetes.io/part-of: litmus rules: # Create and monitor the experiment & helper pods @@ -110,17 +109,17 @@ When the MANAGED_NODEGROUP is enable then the experiment will not try to start t apiVersion: rbac.authorization.k8s.io/v1 kind: ClusterRoleBinding metadata: - name: ec2-terminate-by-id-sa + name: ec2-stop-by-id-sa labels: - name: ec2-terminate-by-id-sa + name: ec2-stop-by-id-sa app.kubernetes.io/part-of: litmus roleRef: apiGroup: rbac.authorization.k8s.io kind: ClusterRole - name: ec2-terminate-by-id-sa + name: ec2-stop-by-id-sa subjects: - kind: ServiceAccount - name: ec2-terminate-by-id-sa + name: ec2-stop-by-id-sa namespace: default ``` @@ -164,7 +163,7 @@ When the MANAGED_NODEGROUP is enable then the experiment will not try to start t CHAOS_INTERVAL - The interval (in sec) between successive instance termination. + The interval (in sec) between successive instance stop. Defaults to 30s @@ -196,9 +195,9 @@ It contains comma separated list of instances IDs subjected to ec2 stop chaos. I Use the following example to tune this: -[embedmd]:# (https://raw.githubusercontent.com/litmuschaos/litmus/master/mkdocs/docs/experiments/categories/aws/ec2-terminate-by-id/instance-id.yaml yaml) +[embedmd]:# (https://raw.githubusercontent.com/litmuschaos/litmus/master/mkdocs/docs/experiments/categories/aws/ec2-stop-by-id/instance-id.yaml yaml) ```yaml -# contains the instance id, to be terminated/stopped +# contains the instance id to be stopped apiVersion: litmuschaos.io/v1alpha1 kind: ChaosEngine metadata: @@ -206,9 +205,9 @@ metadata: spec: engineState: "active" annotationCheck: "false" - chaosServiceAccount: ec2-terminate-by-id-sa + chaosServiceAccount: ec2-stop-by-id-sa experiments: - - name: ec2-terminate-by-id + - name: ec2-stop-by-id spec: components: env: diff --git a/mkdocs/docs/experiments/categories/aws/ec2-terminate-by-id/instance-id.yaml b/mkdocs/docs/experiments/categories/aws/ec2-stop-by-id/instance-id.yaml similarity index 100% rename from mkdocs/docs/experiments/categories/aws/ec2-terminate-by-id/instance-id.yaml rename to mkdocs/docs/experiments/categories/aws/ec2-stop-by-id/instance-id.yaml diff --git a/mkdocs/docs/experiments/categories/aws/ec2-terminate-by-tag.md b/mkdocs/docs/experiments/categories/aws/ec2-stop-by-tag.md similarity index 86% rename from mkdocs/docs/experiments/categories/aws/ec2-terminate-by-tag.md rename to mkdocs/docs/experiments/categories/aws/ec2-stop-by-tag.md index fa287385543..a3b8b6b2154 100644 --- a/mkdocs/docs/experiments/categories/aws/ec2-terminate-by-tag.md +++ b/mkdocs/docs/experiments/categories/aws/ec2-stop-by-tag.md @@ -1,11 +1,11 @@ ## Introduction -- It causes termination of an EC2 instance by tag before bringing it back to running state after the specified chaos duration. +- It causes stopping of an EC2 instance by tag before bringing it back to running state after the specified chaos duration. - It helps to check the performance of the application/process running on the ec2 instance. When the MANAGED_NODEGROUP is enable then the experiment will not try to start the instance post chaos instead it will check of the addition of the new node instance to the cluster. -!!! tip "Scenario: Terminate EC2 Instance" - ![EC2 Terminate By Tag](../../images/ec2-terminate.png) +!!! tip "Scenario: Stop EC2 Instance" + ![EC2 Stop By Tag](../../images/ec2-stop.png) ## Uses @@ -17,7 +17,7 @@ When the MANAGED_NODEGROUP is enable then the experiment will not try to start t ??? info "Verify the prerequisites" - Ensure that Kubernetes Version > 1.16 - Ensure that the Litmus Chaos Operator is running by executing kubectl get pods in operator namespace (typically, litmus).If not, install from here - - Ensure that the ec2-terminate-by-tag experiment resource is available in the cluster by executing kubectl get chaosexperiments in the desired namespace. If not, install from here + - Ensure that the ec2-stop-by-tag experiment resource is available in the cluster by executing kubectl get chaosexperiments in the desired namespace. If not, install from here - Ensure that you have sufficient AWS access to stop and start an ec2 instance. - Ensure to create a Kubernetes secret having the AWS access configuration(key) in the `CHAOS_NAMESPACE`. A sample secret file looks like: @@ -54,24 +54,23 @@ When the MANAGED_NODEGROUP is enable then the experiment will not try to start t ??? note "View the Minimal RBAC permissions" - [embedmd]:# (https://raw.githubusercontent.com/litmuschaos/chaos-charts/master/charts/kube-aws/ec2-terminate-by-tag/rbac.yaml yaml) ```yaml --- apiVersion: v1 kind: ServiceAccount metadata: - name: ec2-terminate-by-tag-sa + name: ec2-stop-by-tag-sa namespace: default labels: - name: ec2-terminate-by-tag-sa + name: ec2-stop-by-tag-sa app.kubernetes.io/part-of: litmus --- apiVersion: rbac.authorization.k8s.io/v1 kind: ClusterRole metadata: - name: ec2-terminate-by-tag-sa + name: ec2-stop-by-tag-sa labels: - name: ec2-terminate-by-tag-sa + name: ec2-stop-by-tag-sa app.kubernetes.io/part-of: litmus rules: # Create and monitor the experiment & helper pods @@ -110,17 +109,17 @@ When the MANAGED_NODEGROUP is enable then the experiment will not try to start t apiVersion: rbac.authorization.k8s.io/v1 kind: ClusterRoleBinding metadata: - name: ec2-terminate-by-tag-sa + name: ec2-stop-by-tag-sa labels: - name: ec2-terminate-by-tag-sa + name: ec2-stop-by-tag-sa app.kubernetes.io/part-of: litmus roleRef: apiGroup: rbac.authorization.k8s.io kind: ClusterRole - name: ec2-terminate-by-tag-sa + name: ec2-stop-by-tag-sa subjects: - kind: ServiceAccount - name: ec2-terminate-by-tag-sa + name: ec2-stop-by-tag-sa namespace: default ``` @@ -201,7 +200,7 @@ It will stop a random single ec2 instance with the given `INSTANCE_TAG` tag and Use the following example to tune this: -[embedmd]:# (https://raw.githubusercontent.com/litmuschaos/litmus/master/mkdocs/docs/experiments/categories/aws/ec2-terminate-by-tag/instance-tag.yaml yaml) +[embedmd]:# (https://raw.githubusercontent.com/litmuschaos/litmus/master/mkdocs/docs/experiments/categories/aws/ec2-stop-by-tag/instance-tag.yaml yaml) ```yaml # target the ec2 instances with matching tag apiVersion: litmuschaos.io/v1alpha1 @@ -213,7 +212,7 @@ spec: annotationCheck: "false" chaosServiceAccount: ec2-terminate-by-tag-sa experiments: - - name: ec2-terminate-by-tag + - name: ec2-stop-by-tag spec: components: env: @@ -233,7 +232,7 @@ It will stop the `INSTANCE_AFFECTED_PERC` percentage of ec2 instances with the g Use the following example to tune this: -[embedmd]:# (https://raw.githubusercontent.com/litmuschaos/litmus/master/mkdocs/docs/experiments/categories/aws/ec2-terminate-by-tag/instance-affected-percentage.yaml yaml) +[embedmd]:# (https://raw.githubusercontent.com/litmuschaos/litmus/master/mkdocs/docs/experiments/categories/aws/ec2-stop-by-tag/instance-affected-percentage.yaml yaml) ```yaml # percentage of ec2 instances, needs to terminate with provided tags apiVersion: litmuschaos.io/v1alpha1 @@ -243,9 +242,9 @@ metadata: spec: engineState: "active" annotationCheck: "false" - chaosServiceAccount: ec2-terminate-by-tag-sa + chaosServiceAccount: ec2-stop-by-tag-sa experiments: - - name: ec2-terminate-by-tag + - name: ec2-stop-by-tag spec: components: env: diff --git a/mkdocs/docs/experiments/categories/aws/ec2-terminate-by-tag/instance-affected-percentage.yaml b/mkdocs/docs/experiments/categories/aws/ec2-stop-by-tag/instance-affected-percentage.yaml similarity index 100% rename from mkdocs/docs/experiments/categories/aws/ec2-terminate-by-tag/instance-affected-percentage.yaml rename to mkdocs/docs/experiments/categories/aws/ec2-stop-by-tag/instance-affected-percentage.yaml diff --git a/mkdocs/docs/experiments/categories/aws/ec2-terminate-by-tag/instance-tag.yaml b/mkdocs/docs/experiments/categories/aws/ec2-stop-by-tag/instance-tag.yaml similarity index 100% rename from mkdocs/docs/experiments/categories/aws/ec2-terminate-by-tag/instance-tag.yaml rename to mkdocs/docs/experiments/categories/aws/ec2-stop-by-tag/instance-tag.yaml diff --git a/mkdocs/docs/experiments/categories/azure/azure-disk-loss.md b/mkdocs/docs/experiments/categories/azure/azure-disk-loss.md index 029d1241ef4..964b0854146 100644 --- a/mkdocs/docs/experiments/categories/azure/azure-disk-loss.md +++ b/mkdocs/docs/experiments/categories/azure/azure-disk-loss.md @@ -17,7 +17,7 @@ ??? info "Verify the prerequisites" - Ensure that Kubernetes Version > 1.16 - Ensure that the Litmus Chaos Operator is running by executing kubectl get pods in operator namespace (typically, litmus).If not, install from here - - Ensure that the azure-disk-loss experiment resource is available in the cluster by executing kubectl get chaosexperiments in the desired namespace. If not, install from here + - Ensure that the azure-disk-loss experiment resource is available in the cluster by executing kubectl get chaosexperiments in the desired namespace. If not, install from here - Ensure that you have sufficient Azure access to detach and attach a disk. - We will use azure [ file-based authentication ](https://docs.microsoft.com/en-us/azure/developer/go/azure-sdk-authorization#use-file-based-authentication) to connect with the instance using azure GO SDK in the experiment. For generating auth file run `az ad sp create-for-rbac --sdk-auth > azure.auth` Azure CLI command. - Ensure to create a Kubernetes secret having the auth file created in the step in `CHAOS_NAMESPACE`. A sample secret file looks like: @@ -57,7 +57,6 @@ ??? note "View the Minimal RBAC permissions" - [embedmd]:# (https://raw.githubusercontent.com/litmuschaos/chaos-charts/master/charts/azure/azure-disk-loss/rbac.yaml yaml) ```yaml --- apiVersion: v1 diff --git a/mkdocs/docs/experiments/categories/azure/azure-instance-stop.md b/mkdocs/docs/experiments/categories/azure/azure-instance-stop.md index 94557aed48e..3e14a8c6903 100644 --- a/mkdocs/docs/experiments/categories/azure/azure-instance-stop.md +++ b/mkdocs/docs/experiments/categories/azure/azure-instance-stop.md @@ -16,7 +16,7 @@ ??? info "Verify the prerequisites" - Ensure that Kubernetes Version > 1.16 - Ensure that the Litmus Chaos Operator is running by executing kubectl get pods in operator namespace (typically, litmus).If not, install from here - - Ensure that the azure-instance-stop experiment resource is available in the cluster by executing kubectl get chaosexperiments in the desired namespace. If not, install from here + - Ensure that the azure-instance-stop experiment resource is available in the cluster by executing kubectl get chaosexperiments in the desired namespace. If not, install from here - Ensure that you have sufficient Azure access to stop and start the an instance. - We will use azure [ file-based authentication ](https://docs.microsoft.com/en-us/azure/developer/go/azure-sdk-authorization#use-file-based-authentication) to connect with the instance using azure GO SDK in the experiment. For generating auth file run `az ad sp create-for-rbac --sdk-auth > azure.auth` Azure CLI command. - Ensure to create a Kubernetes secret having the auth file created in the step in `CHAOS_NAMESPACE`. A sample secret file looks like: @@ -57,7 +57,6 @@ ??? note "View the Minimal RBAC permissions" - [embedmd]:# (https://raw.githubusercontent.com/litmuschaos/chaos-charts/master/charts/azure/azure-instance-stop/rbac.yaml yaml) ```yaml --- apiVersion: v1 diff --git a/mkdocs/docs/experiments/categories/contents.md b/mkdocs/docs/experiments/categories/contents.md index e28e842a150..8c7a1acee48 100644 --- a/mkdocs/docs/experiments/categories/contents.md +++ b/mkdocs/docs/experiments/categories/contents.md @@ -232,14 +232,14 @@ Following Platform Chaos experiments are available: User Guide - EC2 Terminate By ID - Terminate the ec2 instance matched by instance id - ec2-terminate-by-id + EC2 Stop By ID + Stop the EC2 instance matched by instance id + ec2-stop-by-id - EC2 Terminate By Tag - Terminate the ec2 instance matched by instance tag - ec2-terminate-by-tag + EC2 Stop By Tag + Stop the EC2 instance matched by instance tag + ec2-stop-by-tag EBS Loss By ID diff --git a/mkdocs/docs/experiments/categories/gcp/gcp-vm-disk-loss-by-label.md b/mkdocs/docs/experiments/categories/gcp/gcp-vm-disk-loss-by-label.md index 1b117bdb782..461b2ac312e 100644 --- a/mkdocs/docs/experiments/categories/gcp/gcp-vm-disk-loss-by-label.md +++ b/mkdocs/docs/experiments/categories/gcp/gcp-vm-disk-loss-by-label.md @@ -15,7 +15,7 @@ ??? info "Verify the prerequisites" - Ensure that Kubernetes Version > 1.17 - Ensure that the Chaos Operator is running by executing kubectl get pods in operator namespace (typically, litmus).If not, install from here - - Ensure that the gcp-vm-disk-loss-by-label experiment resource is available in the cluster by executing kubectl get chaosexperiments in the desired namespace. If not, install from here + - Ensure that the gcp-vm-disk-loss-by-label experiment resource is available in the cluster by executing kubectl get chaosexperiments in the desired namespace. If not, install from here - Ensure that your service account has an editor access or owner access for the GCP project. - Ensure that the target disk volume is not a boot disk of any VM instance. - Ensure to create a Kubernetes secret having the GCP service account credentials in the default namespace. A sample secret file looks like: @@ -51,7 +51,6 @@ ??? note "View the Minimal RBAC permissions" - [embedmd]:# (https://raw.githubusercontent.com/litmuschaos/chaos-charts/master/charts/gcp/gcp-vm-disk-loss-by-label/rbac.yaml yaml) ```yaml --- apiVersion: v1 diff --git a/mkdocs/docs/experiments/categories/gcp/gcp-vm-disk-loss.md b/mkdocs/docs/experiments/categories/gcp/gcp-vm-disk-loss.md index 9d2f28a8291..2fe564df3cc 100644 --- a/mkdocs/docs/experiments/categories/gcp/gcp-vm-disk-loss.md +++ b/mkdocs/docs/experiments/categories/gcp/gcp-vm-disk-loss.md @@ -15,7 +15,7 @@ ??? info "Verify the prerequisites" - Ensure that Kubernetes Version > 1.16 - Ensure that the Litmus Chaos Operator is running by executing kubectl get pods in operator namespace (typically, litmus).If not, install from here - - Ensure that the gcp-vm-disk-loss experiment resource is available in the cluster by executing kubectl get chaosexperiments in the desired namespace. If not, install from here + - Ensure that the gcp-vm-disk-loss experiment resource is available in the cluster by executing kubectl get chaosexperiments in the desired namespace. If not, install from here - Ensure that your service account has an editor access or owner access for the GCP project. - Ensure that the target disk volume is not a boot disk of any VM instance. - Ensure to create a Kubernetes secret having the GCP service account credentials in the default namespace. A sample secret file looks like: @@ -51,7 +51,6 @@ ??? note "View the Minimal RBAC permissions" - [embedmd]:# (https://raw.githubusercontent.com/litmuschaos/chaos-charts/master/charts/gcp/gcp-vm-disk-loss/rbac.yaml yaml) ```yaml --- apiVersion: v1 diff --git a/mkdocs/docs/experiments/categories/gcp/gcp-vm-instance-stop-by-label.md b/mkdocs/docs/experiments/categories/gcp/gcp-vm-instance-stop-by-label.md index 78d4b0cb7f3..5b30ec83258 100644 --- a/mkdocs/docs/experiments/categories/gcp/gcp-vm-instance-stop-by-label.md +++ b/mkdocs/docs/experiments/categories/gcp/gcp-vm-instance-stop-by-label.md @@ -17,7 +17,7 @@ ??? info "Verify the prerequisites" - Ensure that Kubernetes Version > 1.16 - Ensure that the Litmus Chaos Operator is running by executing kubectl get pods in operator namespace (typically, litmus).If not, install from here - - Ensure that the gcp-vm-instance-stop-by-label experiment resource is available in the cluster by executing kubectl get chaosexperiments in the desired namespace. If not, install from here + - Ensure that the gcp-vm-instance-stop-by-label experiment resource is available in the cluster by executing kubectl get chaosexperiments in the desired namespace. If not, install from here - Ensure that you have sufficient GCP permissions to stop and start the GCP VM instances. - Ensure to create a Kubernetes secret having the GCP service account credentials in the default namespace. A sample secret file looks like: @@ -52,7 +52,6 @@ ??? note "View the Minimal RBAC permissions" - [embedmd]:# (https://raw.githubusercontent.com/litmuschaos/chaos-charts/master/charts/gcp/gcp-vm-instance-stop-by-label/rbac.yaml yaml) ```yaml --- apiVersion: v1 diff --git a/mkdocs/docs/experiments/categories/gcp/gcp-vm-instance-stop.md b/mkdocs/docs/experiments/categories/gcp/gcp-vm-instance-stop.md index 722e2740d2c..9f289f0917d 100644 --- a/mkdocs/docs/experiments/categories/gcp/gcp-vm-instance-stop.md +++ b/mkdocs/docs/experiments/categories/gcp/gcp-vm-instance-stop.md @@ -17,7 +17,7 @@ ??? info "Verify the prerequisites" - Ensure that Kubernetes Version > 1.16 - Ensure that the Litmus Chaos Operator is running by executing kubectl get pods in operator namespace (typically, litmus).If not, install from here - - Ensure that the gcp-vm-instance-stop experiment resource is available in the cluster by executing kubectl get chaosexperiments in the desired namespace. If not, install from here + - Ensure that the gcp-vm-instance-stop experiment resource is available in the cluster by executing kubectl get chaosexperiments in the desired namespace. If not, install from here - Ensure that you have sufficient GCP permissions to stop and start the GCP VM instances. - Ensure to create a Kubernetes secret having the GCP service account credentials in the default namespace. A sample secret file looks like: @@ -52,7 +52,6 @@ ??? note "View the Minimal RBAC permissions" - [embedmd]:# (https://raw.githubusercontent.com/litmuschaos/chaos-charts/master/charts/gcp/gcp-vm-instance-stop/rbac.yaml yaml) ```yaml --- apiVersion: v1 diff --git a/mkdocs/docs/experiments/categories/nodes/docker-service-kill.md b/mkdocs/docs/experiments/categories/nodes/docker-service-kill.md index 33305ed7e6b..1a1f14b9612 100644 --- a/mkdocs/docs/experiments/categories/nodes/docker-service-kill.md +++ b/mkdocs/docs/experiments/categories/nodes/docker-service-kill.md @@ -17,7 +17,7 @@ ??? info "Verify the prerequisites" - Ensure that Kubernetes Version > 1.16 - Ensure that the Litmus Chaos Operator is running by executing kubectl get pods in operator namespace (typically, litmus).If not, install from here - - Ensure that the docker-service-kill experiment resource is available in the cluster by executing kubectl get chaosexperiments in the desired namespace. If not, install from here + - Ensure that the docker-service-kill experiment resource is available in the cluster by executing kubectl get chaosexperiments in the desired namespace. If not, install from here - Ensure that the node specified in the experiment ENV variable TARGET_NODE (the node for which docker service need to be killed) should be cordoned before execution of the chaos experiment (before applying the chaosengine manifest) to ensure that the litmus experiment runner pods are not scheduled on it / subjected to eviction. This can be achieved with the following steps: - Get node names against the applications pods: kubectl get pods -o wide - Cordon the node kubectl cordon <nodename> @@ -34,7 +34,6 @@ ??? note "View the Minimal RBAC permissions" - [embedmd]:# (https://raw.githubusercontent.com/litmuschaos/chaos-charts/master/charts/generic/docker-service-kill/rbac.yaml yaml) ```yaml --- apiVersion: v1 diff --git a/mkdocs/docs/experiments/categories/nodes/kubelet-service-kill.md b/mkdocs/docs/experiments/categories/nodes/kubelet-service-kill.md index 392c521b6a9..4efd7fbc996 100644 --- a/mkdocs/docs/experiments/categories/nodes/kubelet-service-kill.md +++ b/mkdocs/docs/experiments/categories/nodes/kubelet-service-kill.md @@ -17,7 +17,7 @@ ??? info "Verify the prerequisites" - Ensure that Kubernetes Version > 1.16 - Ensure that the Litmus Chaos Operator is running by executing kubectl get pods in operator namespace (typically, litmus).If not, install from here - - Ensure that the kubelet-service-kill experiment resource is available in the cluster by executing kubectl get chaosexperiments in the desired namespace. If not, install from here + - Ensure that the kubelet-service-kill experiment resource is available in the cluster by executing kubectl get chaosexperiments in the desired namespace. If not, install from here - Ensure that the node specified in the experiment ENV variable TARGET_NODE (the node for which kubelet service need to be killed) should be cordoned before execution of the chaos experiment (before applying the chaosengine manifest) to ensure that the litmus experiment runner pods are not scheduled on it / subjected to eviction. This can be achieved with the following steps: - Get node names against the applications pods: kubectl get pods -o wide - Cordon the node kubectl cordon <nodename> @@ -34,7 +34,6 @@ ??? note "View the Minimal RBAC permissions" - [embedmd]:# (https://raw.githubusercontent.com/litmuschaos/chaos-charts/master/charts/generic/kubelet-service-kill/rbac.yaml yaml) ```yaml --- apiVersion: v1 diff --git a/mkdocs/docs/experiments/categories/nodes/node-cpu-hog.md b/mkdocs/docs/experiments/categories/nodes/node-cpu-hog.md index 8eec9ef7bea..4c5a38ab8f0 100644 --- a/mkdocs/docs/experiments/categories/nodes/node-cpu-hog.md +++ b/mkdocs/docs/experiments/categories/nodes/node-cpu-hog.md @@ -17,7 +17,7 @@ Application implies services. Can be reframed as: Tests application resiliency u ??? info "Verify the prerequisites" - Ensure that Kubernetes Version > 1.16 - Ensure that the Litmus Chaos Operator is running by executing kubectl get pods in operator namespace (typically, litmus).If not, install from here - - Ensure that the node-cpu-hog experiment resource is available in the cluster by executing kubectl get chaosexperiments in the desired namespace. If not, install from here + - Ensure that the node-cpu-hog experiment resource is available in the cluster by executing kubectl get chaosexperiments in the desired namespace. If not, install from here ## Default Validations @@ -31,7 +31,6 @@ Application implies services. Can be reframed as: Tests application resiliency u ??? note "View the Minimal RBAC permissions" - [embedmd]:# (https://raw.githubusercontent.com/litmuschaos/chaos-charts/master/charts/generic/node-cpu-hog/rbac.yaml yaml) ```yaml --- apiVersion: v1 diff --git a/mkdocs/docs/experiments/categories/nodes/node-drain.md b/mkdocs/docs/experiments/categories/nodes/node-drain.md index 879fd39bf7e..844ce0e1547 100644 --- a/mkdocs/docs/experiments/categories/nodes/node-drain.md +++ b/mkdocs/docs/experiments/categories/nodes/node-drain.md @@ -15,7 +15,7 @@ ??? info "Verify the prerequisites" - Ensure that Kubernetes Version > 1.16 - Ensure that the Litmus Chaos Operator is running by executing kubectl get pods in operator namespace (typically, litmus).If not, install from here - - Ensure that the node-drain experiment resource is available in the cluster by executing kubectl get chaosexperiments in the desired namespace. If not, install from here + - Ensure that the node-drain experiment resource is available in the cluster by executing kubectl get chaosexperiments in the desired namespace. If not, install from here - Ensure that the node specified in the experiment ENV variable TARGET_NODE (the node which will be drained) should be cordoned before execution of the chaos experiment (before applying the chaosengine manifest) to ensure that the litmus experiment runner pods are not scheduled on it / subjected to eviction. This can be achieved with the following steps: - Get node names against the applications pods: kubectl get pods -o wide - Cordon the node kubectl cordon <nodename> @@ -32,7 +32,6 @@ ??? note "View the Minimal RBAC permissions" - [embedmd]:# (https://raw.githubusercontent.com/litmuschaos/chaos-charts/master/charts/generic/node-drain/rbac.yaml yaml) ```yaml --- apiVersion: v1 diff --git a/mkdocs/docs/experiments/categories/nodes/node-io-stress.md b/mkdocs/docs/experiments/categories/nodes/node-io-stress.md index b9011f9992d..5bd208a3ca5 100644 --- a/mkdocs/docs/experiments/categories/nodes/node-io-stress.md +++ b/mkdocs/docs/experiments/categories/nodes/node-io-stress.md @@ -17,7 +17,7 @@ ??? info "Verify the prerequisites" - Ensure that Kubernetes Version > 1.16 - Ensure that the Litmus Chaos Operator is running by executing kubectl get pods in operator namespace (typically, litmus).If not, install from here - - Ensure that the node-io-stress experiment resource is available in the cluster by executing kubectl get chaosexperiments in the desired namespace. If not, install from here + - Ensure that the node-io-stress experiment resource is available in the cluster by executing kubectl get chaosexperiments in the desired namespace. If not, install from here ## Default Validations @@ -31,7 +31,6 @@ ??? note "View the Minimal RBAC permissions" - [embedmd]:# (https://raw.githubusercontent.com/litmuschaos/chaos-charts/master/charts/generic/node-io-stress/rbac.yaml yaml) ```yaml --- apiVersion: v1 diff --git a/mkdocs/docs/experiments/categories/nodes/node-memory-hog.md b/mkdocs/docs/experiments/categories/nodes/node-memory-hog.md index 11620a69066..c1767190338 100644 --- a/mkdocs/docs/experiments/categories/nodes/node-memory-hog.md +++ b/mkdocs/docs/experiments/categories/nodes/node-memory-hog.md @@ -17,7 +17,7 @@ ??? info "Verify the prerequisites" - Ensure that Kubernetes Version > 1.16 - Ensure that the Litmus Chaos Operator is running by executing kubectl get pods in operator namespace (typically, litmus).If not, install from here - - Ensure that the node-memory-hog experiment resource is available in the cluster by executing kubectl get chaosexperiments in the desired namespace. If not, install from here + - Ensure that the node-memory-hog experiment resource is available in the cluster by executing kubectl get chaosexperiments in the desired namespace. If not, install from here ## Default Validations @@ -31,7 +31,6 @@ ??? note "View the Minimal RBAC permissions" - [embedmd]:# (https://raw.githubusercontent.com/litmuschaos/chaos-charts/master/charts/generic/node-memory-hog/rbac.yaml yaml) ```yaml --- apiVersion: v1 diff --git a/mkdocs/docs/experiments/categories/nodes/node-restart.md b/mkdocs/docs/experiments/categories/nodes/node-restart.md index c1d7122509d..85850d5ffbf 100644 --- a/mkdocs/docs/experiments/categories/nodes/node-restart.md +++ b/mkdocs/docs/experiments/categories/nodes/node-restart.md @@ -17,7 +17,7 @@ ??? info "Verify the prerequisites" - Ensure that Kubernetes Version > 1.16 - Ensure that the Litmus Chaos Operator is running by executing kubectl get pods in operator namespace (typically, litmus).If not, install from here - - Ensure that the node-restart experiment resource is available in the cluster by executing kubectl get chaosexperiments in the desired namespace. If not, install from here + - Ensure that the node-restart experiment resource is available in the cluster by executing kubectl get chaosexperiments in the desired namespace. If not, install from here - Create a Kubernetes secret named `id-rsa` where the experiment will run, where its contents will be the private SSH key for `SSH_USER` used to connect to the node that hosts the target pod in the secret field `ssh-privatekey`. A sample secret is shown below: ```yaml @@ -56,7 +56,6 @@ ??? note "View the Minimal RBAC permissions" - [embedmd]:# (https://raw.githubusercontent.com/litmuschaos/chaos-charts/master/charts/generic/node-restart/rbac.yaml yaml) ```yaml --- apiVersion: v1 diff --git a/mkdocs/docs/experiments/categories/nodes/node-taint.md b/mkdocs/docs/experiments/categories/nodes/node-taint.md index 119ba5fa2fa..4a73c958219 100644 --- a/mkdocs/docs/experiments/categories/nodes/node-taint.md +++ b/mkdocs/docs/experiments/categories/nodes/node-taint.md @@ -15,7 +15,7 @@ ??? info "Verify the prerequisites" - Ensure that Kubernetes Version > 1.16 - Ensure that the Litmus Chaos Operator is running by executing kubectl get pods in operator namespace (typically, litmus).If not, install from here - - Ensure that the node-taint experiment resource is available in the cluster by executing kubectl get chaosexperiments in the desired namespace. If not, install from here + - Ensure that the node-taint experiment resource is available in the cluster by executing kubectl get chaosexperiments in the desired namespace. If not, install from here - Ensure that the node specified in the experiment ENV variable TARGET_NODE (the node which will be tainted) should be cordoned before execution of the chaos experiment (before applying the chaosengine manifest) to ensure that the litmus experiment runner pods are not scheduled on it / subjected to eviction. This can be achieved with the following steps: - Get node names against the applications pods: kubectl get pods -o wide - Cordon the node kubectl cordon <nodename> @@ -32,7 +32,6 @@ ??? note "View the Minimal RBAC permissions" - [embedmd]:# (https://raw.githubusercontent.com/litmuschaos/chaos-charts/master/charts/generic/node-taint/rbac.yaml yaml) ```yaml --- apiVersion: v1 diff --git a/mkdocs/docs/experiments/categories/pods/container-kill.md b/mkdocs/docs/experiments/categories/pods/container-kill.md index feab3e7a7eb..b0d6b2f7452 100644 --- a/mkdocs/docs/experiments/categories/pods/container-kill.md +++ b/mkdocs/docs/experiments/categories/pods/container-kill.md @@ -17,7 +17,7 @@ ??? info "Verify the prerequisites" - Ensure that Kubernetes Version > 1.16 - Ensure that the Litmus Chaos Operator is running by executing kubectl get pods in operator namespace (typically, litmus).If not, install from here - - Ensure that the container-kill experiment resource is available in the cluster by executing kubectl get chaosexperiments in the desired namespace. If not, install from here + - Ensure that the container-kill experiment resource is available in the cluster by executing kubectl get chaosexperiments in the desired namespace. If not, install from here ## Default Validations @@ -31,7 +31,6 @@ ??? note "View the Minimal RBAC permissions" - [embedmd]:# (https://raw.githubusercontent.com/litmuschaos/chaos-charts/master/charts/generic/container-kill/rbac.yaml yaml) ```yaml --- apiVersion: v1 diff --git a/mkdocs/docs/experiments/categories/pods/disk-fill.md b/mkdocs/docs/experiments/categories/pods/disk-fill.md index a67492d25e5..b7d550fb72b 100644 --- a/mkdocs/docs/experiments/categories/pods/disk-fill.md +++ b/mkdocs/docs/experiments/categories/pods/disk-fill.md @@ -18,7 +18,7 @@ ??? info "Verify the prerequisites" - Ensure that Kubernetes Version > 1.16 - Ensure that the Litmus Chaos Operator is running by executing kubectl get pods in operator namespace (typically, litmus).If not, install from here - - Ensure that the disk-fill experiment resource is available in the cluster by executing kubectl get chaosexperiments in the desired namespace. If not, install from here + - Ensure that the disk-fill experiment resource is available in the cluster by executing kubectl get chaosexperiments in the desired namespace. If not, install from here - Appropriate Ephemeral Storage Requests and Limits should be set for the application before running the experiment. An example specification is shown below: ```yaml apiVersion: v1 @@ -58,7 +58,6 @@ ??? note "View the Minimal RBAC permissions" - [embedmd]:# (https://raw.githubusercontent.com/litmuschaos/chaos-charts/master/charts/generic/disk-fill/rbac.yaml yaml) ```yaml --- apiVersion: v1 diff --git a/mkdocs/docs/experiments/categories/pods/pod-autoscaler.md b/mkdocs/docs/experiments/categories/pods/pod-autoscaler.md index 043c1b58529..16b3f472376 100644 --- a/mkdocs/docs/experiments/categories/pods/pod-autoscaler.md +++ b/mkdocs/docs/experiments/categories/pods/pod-autoscaler.md @@ -17,7 +17,7 @@ ??? info "Verify the prerequisites" - Ensure that Kubernetes Version > 1.16 - Ensure that the Litmus Chaos Operator is running by executing kubectl get pods in operator namespace (typically, litmus).If not, install from here - - Ensure that the pod-autoscaler experiment resource is available in the cluster by executing kubectl get chaosexperiments in the desired namespace. If not, install from here + - Ensure that the pod-autoscaler experiment resource is available in the cluster by executing kubectl get chaosexperiments in the desired namespace. If not, install from here ## Default Validations @@ -31,7 +31,6 @@ ??? note "View the Minimal RBAC permissions" - [embedmd]:# (https://raw.githubusercontent.com/litmuschaos/chaos-charts/master/charts/generic/pod-autoscaler/rbac.yaml yaml) ```yaml --- apiVersion: v1 diff --git a/mkdocs/docs/experiments/categories/pods/pod-cpu-hog-exec.md b/mkdocs/docs/experiments/categories/pods/pod-cpu-hog-exec.md index ee53cad6df5..29ddf3786df 100644 --- a/mkdocs/docs/experiments/categories/pods/pod-cpu-hog-exec.md +++ b/mkdocs/docs/experiments/categories/pods/pod-cpu-hog-exec.md @@ -19,7 +19,7 @@ ??? info "Verify the prerequisites" - Ensure that Kubernetes Version > 1.16 - Ensure that the Litmus Chaos Operator is running by executing kubectl get pods in operator namespace (typically, litmus).If not, install from here - - Ensure that the pod-cpu-hog-exec experiment resource is available in the cluster by executing kubectl get chaosexperiments in the desired namespace. If not, install from here + - Ensure that the pod-cpu-hog-exec experiment resource is available in the cluster by executing kubectl get chaosexperiments in the desired namespace. If not, install from here ## Default Validations @@ -33,7 +33,6 @@ ??? note "View the Minimal RBAC permissions" - [embedmd]:# (https://raw.githubusercontent.com/litmuschaos/chaos-charts/master/charts/generic/pod-cpu-hog-exec/rbac.yaml yaml) ```yaml --- apiVersion: v1 diff --git a/mkdocs/docs/experiments/categories/pods/pod-cpu-hog.md b/mkdocs/docs/experiments/categories/pods/pod-cpu-hog.md index 567f46e9a0c..e1aa7f756ca 100644 --- a/mkdocs/docs/experiments/categories/pods/pod-cpu-hog.md +++ b/mkdocs/docs/experiments/categories/pods/pod-cpu-hog.md @@ -19,7 +19,7 @@ ??? info "Verify the prerequisites" - Ensure that Kubernetes Version > 1.16 - Ensure that the Litmus Chaos Operator is running by executing kubectl get pods in operator namespace (typically, litmus).If not, install from here - - Ensure that the pod-cpu-hog experiment resource is available in the cluster by executing kubectl get chaosexperiments in the desired namespace. If not, install from here + - Ensure that the pod-cpu-hog experiment resource is available in the cluster by executing kubectl get chaosexperiments in the desired namespace. If not, install from here ## Default Validations @@ -33,7 +33,6 @@ ??? note "View the Minimal RBAC permissions" - [embedmd]:# (https://raw.githubusercontent.com/litmuschaos/chaos-charts/master/charts/generic/pod-cpu-hog/rbac.yaml yaml) ```yaml --- apiVersion: v1 diff --git a/mkdocs/docs/experiments/categories/pods/pod-delete.md b/mkdocs/docs/experiments/categories/pods/pod-delete.md index 7ed725100b1..edc0a442e96 100644 --- a/mkdocs/docs/experiments/categories/pods/pod-delete.md +++ b/mkdocs/docs/experiments/categories/pods/pod-delete.md @@ -19,7 +19,7 @@ ??? info "Verify the prerequisites" - Ensure that Kubernetes Version > 1.16 - Ensure that the Litmus Chaos Operator is running by executing kubectl get pods in operator namespace (typically, litmus).If not, install from here - - Ensure that the pod-delete experiment resource is available in the cluster by executing kubectl get chaosexperiments in the desired namespace. If not, install from here + - Ensure that the pod-delete experiment resource is available in the cluster by executing kubectl get chaosexperiments in the desired namespace. If not, install from here ## Default Validations @@ -33,7 +33,6 @@ ??? note "View the Minimal RBAC permissions" - [embedmd]:# (https://raw.githubusercontent.com/litmuschaos/chaos-charts/master/charts/generic/pod-delete/rbac.yaml yaml) ```yaml --- apiVersion: v1 diff --git a/mkdocs/docs/experiments/categories/pods/pod-dns-error.md b/mkdocs/docs/experiments/categories/pods/pod-dns-error.md index f7cb0df6a2f..77ea7b63af7 100644 --- a/mkdocs/docs/experiments/categories/pods/pod-dns-error.md +++ b/mkdocs/docs/experiments/categories/pods/pod-dns-error.md @@ -16,7 +16,7 @@ ??? info "Verify the prerequisites" - Ensure that Kubernetes Version > 1.16 - Ensure that the Litmus Chaos Operator is running by executing kubectl get pods in operator namespace (typically, litmus).If not, install from here - - Ensure that the pod-dns-error experiment resource is available in the cluster by executing kubectl get chaosexperiments in the desired namespace. If not, install from here + - Ensure that the pod-dns-error experiment resource is available in the cluster by executing kubectl get chaosexperiments in the desired namespace. If not, install from here ## Default Validations @@ -30,7 +30,6 @@ ??? note "View the Minimal RBAC permissions" - [embedmd]:# (https://raw.githubusercontent.com/litmuschaos/chaos-charts/master/charts/generic/pod-dns-error/rbac.yaml yaml) ```yaml --- apiVersion: v1 diff --git a/mkdocs/docs/experiments/categories/pods/pod-dns-spoof.md b/mkdocs/docs/experiments/categories/pods/pod-dns-spoof.md index cb978d0bcec..f6a533e27e0 100644 --- a/mkdocs/docs/experiments/categories/pods/pod-dns-spoof.md +++ b/mkdocs/docs/experiments/categories/pods/pod-dns-spoof.md @@ -16,7 +16,7 @@ ??? info "Verify the prerequisites" - Ensure that Kubernetes Version > 1.16 - Ensure that the Litmus Chaos Operator is running by executing kubectl get pods in operator namespace (typically, litmus).If not, install from here - - Ensure that the pod-dns-spoof experiment resource is available in the cluster by executing kubectl get chaosexperiments in the desired namespace. If not, install from here + - Ensure that the pod-dns-spoof experiment resource is available in the cluster by executing kubectl get chaosexperiments in the desired namespace. If not, install from here ## Default Validations @@ -30,7 +30,6 @@ ??? note "View the Minimal RBAC permissions" - [embedmd]:# (https://raw.githubusercontent.com/litmuschaos/chaos-charts/master/charts/generic/pod-dns-spoof/rbac.yaml yaml) ```yaml --- apiVersion: v1 diff --git a/mkdocs/docs/experiments/categories/pods/pod-http-latency.md b/mkdocs/docs/experiments/categories/pods/pod-http-latency.md index 7e51175c395..2cc8e4b9cec 100644 --- a/mkdocs/docs/experiments/categories/pods/pod-http-latency.md +++ b/mkdocs/docs/experiments/categories/pods/pod-http-latency.md @@ -16,7 +16,7 @@ ??? info "Verify the prerequisites" - Ensure that Kubernetes Version > 1.17 - Ensure that the Litmus Chaos Operator is running by executing kubectl get pods in operator namespace (typically, litmus).If not, install from here - - Ensure that the pod-http-latency experiment resource is available in the cluster by executing kubectl get chaosexperiments in the desired namespace. If not, install from here + - Ensure that the pod-http-latency experiment resource is available in the cluster by executing kubectl get chaosexperiments in the desired namespace. If not, install from here ## Default Validations @@ -30,7 +30,6 @@ ??? note "View the Minimal RBAC permissions" - [embedmd]:# (https://raw.githubusercontent.com/litmuschaos/chaos-charts/master/charts/generic/pod-http-latency/rbac.yaml yaml) ```yaml --- apiVersion: v1 diff --git a/mkdocs/docs/experiments/categories/pods/pod-http-modify-body.md b/mkdocs/docs/experiments/categories/pods/pod-http-modify-body.md index 7172b34bbdb..7a4ae1ba144 100644 --- a/mkdocs/docs/experiments/categories/pods/pod-http-modify-body.md +++ b/mkdocs/docs/experiments/categories/pods/pod-http-modify-body.md @@ -17,7 +17,7 @@ ??? info "Verify the prerequisites" - Ensure that Kubernetes Version > 1.17 - Ensure that the Litmus Chaos Operator is running by executing kubectl get pods in operator namespace (typically, litmus).If not, install from here - - Ensure that the pod-http-modify-body experiment resource is available in the cluster by executing kubectl get chaosexperiments in the desired namespace. If not, install from here + - Ensure that the pod-http-modify-body experiment resource is available in the cluster by executing kubectl get chaosexperiments in the desired namespace. If not, install from here ## Default Validations @@ -31,7 +31,6 @@ ??? note "View the Minimal RBAC permissions" - [embedmd]:# (https://raw.githubusercontent.com/litmuschaos/chaos-charts/master/charts/generic/pod-http-modify-body/rbac.yaml yaml) ```yaml --- apiVersion: v1 diff --git a/mkdocs/docs/experiments/categories/pods/pod-http-modify-header.md b/mkdocs/docs/experiments/categories/pods/pod-http-modify-header.md index 6bd619395c6..8455fb22f14 100644 --- a/mkdocs/docs/experiments/categories/pods/pod-http-modify-header.md +++ b/mkdocs/docs/experiments/categories/pods/pod-http-modify-header.md @@ -16,7 +16,7 @@ ??? info "Verify the prerequisites" - Ensure that Kubernetes Version > 1.17 - Ensure that the Litmus Chaos Operator is running by executing kubectl get pods in operator namespace (typically, litmus).If not, install from here - - Ensure that the pod-http-modify-header experiment resource is available in the cluster by executing kubectl get chaosexperiments in the desired namespace. If not, install from here + - Ensure that the pod-http-modify-header experiment resource is available in the cluster by executing kubectl get chaosexperiments in the desired namespace. If not, install from here ## Default Validations @@ -30,7 +30,6 @@ ??? note "View the Minimal RBAC permissions" - [embedmd]:# (https://raw.githubusercontent.com/litmuschaos/chaos-charts/master/charts/generic/pod-http-modify-header/rbac.yaml yaml) ```yaml --- apiVersion: v1 diff --git a/mkdocs/docs/experiments/categories/pods/pod-http-reset-peer.md b/mkdocs/docs/experiments/categories/pods/pod-http-reset-peer.md index cffa0704418..b6505dc9869 100644 --- a/mkdocs/docs/experiments/categories/pods/pod-http-reset-peer.md +++ b/mkdocs/docs/experiments/categories/pods/pod-http-reset-peer.md @@ -16,7 +16,7 @@ ??? info "Verify the prerequisites" - Ensure that Kubernetes Version > 1.17 - Ensure that the Litmus Chaos Operator is running by executing kubectl get pods in operator namespace (typically, litmus).If not, install from here - - Ensure that the pod-http-reset-peer experiment resource is available in the cluster by executing kubectl get chaosexperiments in the desired namespace. If not, install from here + - Ensure that the pod-http-reset-peer experiment resource is available in the cluster by executing kubectl get chaosexperiments in the desired namespace. If not, install from here ## Default Validations @@ -30,7 +30,6 @@ ??? note "View the Minimal RBAC permissions" - [embedmd]:# (https://raw.githubusercontent.com/litmuschaos/chaos-charts/master/charts/generic/pod-http-reset-peer/rbac.yaml yaml) ```yaml --- apiVersion: v1 diff --git a/mkdocs/docs/experiments/categories/pods/pod-http-status-code.md b/mkdocs/docs/experiments/categories/pods/pod-http-status-code.md index b7d12cf01a4..5c96b04c63b 100644 --- a/mkdocs/docs/experiments/categories/pods/pod-http-status-code.md +++ b/mkdocs/docs/experiments/categories/pods/pod-http-status-code.md @@ -16,7 +16,7 @@ ??? info "Verify the prerequisites" - Ensure that Kubernetes Version > 1.17 - Ensure that the Litmus Chaos Operator is running by executing kubectl get pods in operator namespace (typically, litmus).If not, install from here - - Ensure that the pod-http-status-code experiment resource is available in the cluster by executing kubectl get chaosexperiments in the desired namespace. If not, install from here + - Ensure that the pod-http-status-code experiment resource is available in the cluster by executing kubectl get chaosexperiments in the desired namespace. If not, install from here ## Default Validations @@ -30,7 +30,6 @@ ??? note "View the Minimal RBAC permissions" - [embedmd]:# (https://raw.githubusercontent.com/litmuschaos/chaos-charts/master/charts/generic/pod-http-status-code/rbac.yaml yaml) ```yaml --- apiVersion: v1 diff --git a/mkdocs/docs/experiments/categories/pods/pod-io-stress.md b/mkdocs/docs/experiments/categories/pods/pod-io-stress.md index e9f441e31a8..7adcf720dc7 100644 --- a/mkdocs/docs/experiments/categories/pods/pod-io-stress.md +++ b/mkdocs/docs/experiments/categories/pods/pod-io-stress.md @@ -17,7 +17,7 @@ ??? info "Verify the prerequisites" - Ensure that Kubernetes Version > 1.16 - Ensure that the Litmus Chaos Operator is running by executing kubectl get pods in operator namespace (typically, litmus).If not, install from here - - Ensure that the pod-io-stress experiment resource is available in the cluster by executing kubectl get chaosexperiments in the desired namespace. If not, install from here + - Ensure that the pod-io-stress experiment resource is available in the cluster by executing kubectl get chaosexperiments in the desired namespace. If not, install from here ## Default Validations @@ -31,7 +31,6 @@ ??? note "View the Minimal RBAC permissions" - [embedmd]:# (https://raw.githubusercontent.com/litmuschaos/chaos-charts/master/charts/generic/pod-io-stress/rbac.yaml yaml) ```yaml --- apiVersion: v1 diff --git a/mkdocs/docs/experiments/categories/pods/pod-memory-hog-exec.md b/mkdocs/docs/experiments/categories/pods/pod-memory-hog-exec.md index 8d813a73cd1..d4246b87b81 100644 --- a/mkdocs/docs/experiments/categories/pods/pod-memory-hog-exec.md +++ b/mkdocs/docs/experiments/categories/pods/pod-memory-hog-exec.md @@ -19,7 +19,7 @@ ??? info "Verify the prerequisites" - Ensure that Kubernetes Version > 1.16 - Ensure that the Litmus Chaos Operator is running by executing kubectl get pods in operator namespace (typically, litmus).If not, install from here - - Ensure that the pod-memory-hog-exec experiment resource is available in the cluster by executing kubectl get chaosexperiments in the desired namespace. If not, install from here + - Ensure that the pod-memory-hog-exec experiment resource is available in the cluster by executing kubectl get chaosexperiments in the desired namespace. If not, install from here ## Default Validations @@ -33,7 +33,6 @@ ??? note "View the Minimal RBAC permissions" - [embedmd]:# (https://raw.githubusercontent.com/litmuschaos/chaos-charts/master/charts/generic/pod-memory-hog-exec/rbac.yaml yaml) ```yaml --- apiVersion: v1 diff --git a/mkdocs/docs/experiments/categories/pods/pod-memory-hog.md b/mkdocs/docs/experiments/categories/pods/pod-memory-hog.md index 88a6f0508ed..fbfad05c093 100644 --- a/mkdocs/docs/experiments/categories/pods/pod-memory-hog.md +++ b/mkdocs/docs/experiments/categories/pods/pod-memory-hog.md @@ -18,7 +18,7 @@ ??? info "Verify the prerequisites" - Ensure that Kubernetes Version > 1.16 - Ensure that the Litmus Chaos Operator is running by executing kubectl get pods in operator namespace (typically, litmus).If not, install from here - - Ensure that the pod-memory-hog experiment resource is available in the cluster by executing kubectl get chaosexperiments in the desired namespace. If not, install from here + - Ensure that the pod-memory-hog experiment resource is available in the cluster by executing kubectl get chaosexperiments in the desired namespace. If not, install from here ## Default Validations @@ -32,7 +32,6 @@ ??? note "View the Minimal RBAC permissions" - [embedmd]:# (https://raw.githubusercontent.com/litmuschaos/chaos-charts/master/charts/generic/pod-memory-hog/rbac.yaml yaml) ```yaml --- apiVersion: v1 diff --git a/mkdocs/docs/experiments/categories/pods/pod-network-corruption.md b/mkdocs/docs/experiments/categories/pods/pod-network-corruption.md index 5e95da5d245..e9077e62bff 100644 --- a/mkdocs/docs/experiments/categories/pods/pod-network-corruption.md +++ b/mkdocs/docs/experiments/categories/pods/pod-network-corruption.md @@ -16,7 +16,7 @@ ??? info "Verify the prerequisites" - Ensure that Kubernetes Version > 1.16 - Ensure that the Litmus Chaos Operator is running by executing kubectl get pods in operator namespace (typically, litmus).If not, install from here - - Ensure that the pod-network-corruption experiment resource is available in the cluster by executing kubectl get chaosexperiments in the desired namespace. If not, install from here + - Ensure that the pod-network-corruption experiment resource is available in the cluster by executing kubectl get chaosexperiments in the desired namespace. If not, install from here ## Default Validations @@ -30,7 +30,6 @@ ??? note "View the Minimal RBAC permissions" - [embedmd]:# (https://raw.githubusercontent.com/litmuschaos/chaos-charts/master/charts/generic/pod-network-corruption/rbac.yaml yaml) ```yaml --- apiVersion: v1 diff --git a/mkdocs/docs/experiments/categories/pods/pod-network-duplication.md b/mkdocs/docs/experiments/categories/pods/pod-network-duplication.md index 3c2e16a6991..e023a6a303e 100644 --- a/mkdocs/docs/experiments/categories/pods/pod-network-duplication.md +++ b/mkdocs/docs/experiments/categories/pods/pod-network-duplication.md @@ -16,7 +16,7 @@ ??? info "Verify the prerequisites" - Ensure that Kubernetes Version > 1.16 - Ensure that the Litmus Chaos Operator is running by executing kubectl get pods in operator namespace (typically, litmus).If not, install from here - - Ensure that the pod-network-duplication experiment resource is available in the cluster by executing kubectl get chaosexperiments in the desired namespace. If not, install from here + - Ensure that the pod-network-duplication experiment resource is available in the cluster by executing kubectl get chaosexperiments in the desired namespace. If not, install from here ## Default Validations @@ -30,7 +30,6 @@ ??? note "View the Minimal RBAC permissions" - [embedmd]:# (https://raw.githubusercontent.com/litmuschaos/chaos-charts/master/charts/generic/pod-network-duplication/rbac.yaml yaml) ```yaml apiVersion: v1 kind: ServiceAccount diff --git a/mkdocs/docs/experiments/categories/pods/pod-network-latency.md b/mkdocs/docs/experiments/categories/pods/pod-network-latency.md index beed3a1517d..6d85b232520 100644 --- a/mkdocs/docs/experiments/categories/pods/pod-network-latency.md +++ b/mkdocs/docs/experiments/categories/pods/pod-network-latency.md @@ -21,7 +21,7 @@ ??? info "Verify the prerequisites" - Ensure that Kubernetes Version > 1.16 - Ensure that the Litmus Chaos Operator is running by executing kubectl get pods in operator namespace (typically, litmus).If not, install from here - - Ensure that the pod-network-latency experiment resource is available in the cluster by executing kubectl get chaosexperiments in the desired namespace. If not, install from here + - Ensure that the pod-network-latency experiment resource is available in the cluster by executing kubectl get chaosexperiments in the desired namespace. If not, install from here ## Default Validations @@ -35,7 +35,6 @@ ??? note "View the Minimal RBAC permissions" - [embedmd]:# (https://raw.githubusercontent.com/litmuschaos/chaos-charts/master/charts/generic/pod-network-latency/rbac.yaml yaml) ```yaml --- apiVersion: v1 diff --git a/mkdocs/docs/experiments/categories/pods/pod-network-loss.md b/mkdocs/docs/experiments/categories/pods/pod-network-loss.md index 074392c9aa5..97660365140 100644 --- a/mkdocs/docs/experiments/categories/pods/pod-network-loss.md +++ b/mkdocs/docs/experiments/categories/pods/pod-network-loss.md @@ -16,7 +16,7 @@ ??? info "Verify the prerequisites" - Ensure that Kubernetes Version > 1.16 - Ensure that the Litmus Chaos Operator is running by executing kubectl get pods in operator namespace (typically, litmus).If not, install from here - - Ensure that the pod-network-loss experiment resource is available in the cluster by executing kubectl get chaosexperiments in the desired namespace. If not, install from here + - Ensure that the pod-network-loss experiment resource is available in the cluster by executing kubectl get chaosexperiments in the desired namespace. If not, install from here ## Default Validations @@ -30,7 +30,6 @@ ??? note "View the Minimal RBAC permissions" - [embedmd]:# (https://raw.githubusercontent.com/litmuschaos/chaos-charts/master/charts/generic/pod-network-loss/rbac.yaml yaml) ```yaml apiVersion: v1 kind: ServiceAccount diff --git a/mkdocs/docs/experiments/categories/pods/pod-network-partition.md b/mkdocs/docs/experiments/categories/pods/pod-network-partition.md index 98b6e4a871a..cff1b1c9bb5 100644 --- a/mkdocs/docs/experiments/categories/pods/pod-network-partition.md +++ b/mkdocs/docs/experiments/categories/pods/pod-network-partition.md @@ -16,7 +16,7 @@ ??? info "Verify the prerequisites" - Ensure that Kubernetes Version > 1.16 - Ensure that the Litmus Chaos Operator is running by executing kubectl get pods in operator namespace (typically, litmus).If not, install from here - - Ensure that the pod-network-partition experiment resource is available in the cluster by executing kubectl get chaosexperiments in the desired namespace. If not, install from here + - Ensure that the pod-network-partition experiment resource is available in the cluster by executing kubectl get chaosexperiments in the desired namespace. If not, install from here ## Default Validations @@ -30,7 +30,6 @@ ??? note "View the Minimal RBAC permissions" - [embedmd]:# (https://raw.githubusercontent.com/litmuschaos/chaos-charts/master/charts/generic/pod-network-partition/rbac.yaml yaml) ```yaml apiVersion: v1 kind: ServiceAccount diff --git a/mkdocs/docs/experiments/categories/spring-boot/spring-boot-app-kill.md b/mkdocs/docs/experiments/categories/spring-boot/spring-boot-app-kill.md index 910c082f631..7f5e63af53f 100644 --- a/mkdocs/docs/experiments/categories/spring-boot/spring-boot-app-kill.md +++ b/mkdocs/docs/experiments/categories/spring-boot/spring-boot-app-kill.md @@ -16,7 +16,7 @@