+
+ | Tunable |
+ Description |
+ Notes |
+
+
+ | EC2_INSTANCE_ID / EC2_INSTANCE_TAG |
+ ID or tag of the target EC2 instance(s). |
+ For example, i-044d3cb4b03b8af1f or a tag key-value. For more information, go to EC2 instance ID. |
+
+
+ | REGION |
+ The AWS region ID where the EC2 instance has been created. |
+ For example, us-east-1. For more information, go to region. |
+
+
+ | PROCESS_IDS / PROCESS_NAMES |
+ Process IDs or names of the target processes (comma-separated). |
+ For example, 183,253,857 or notepad,explorer. For more information, go to process IDs or process names. |
+
+
+
+### Optional tunables
+
+
+
+ | Tunable |
+ Description |
+ Notes |
+
+
+ | TOTAL_CHAOS_DURATION |
+ Duration for which chaos is injected (in seconds). |
+ Default: 60 s. For more information, go to duration of the chaos. |
+
+
+ | INSTANCE_AFFECTED_PERC |
+ Percentage of instances to target (if using tags). |
+ Optional. For more information, go to instance affected perc. |
+
+
+ | FORCE |
+ Force kill the process. |
+ Default: disable. For example: enable. For more information, go to force . |
+
+
+ | INSTALL_DEPENDENCIES |
+ Install dependencies on the target instance. |
+ Default: true. For more information, go to install dependencies. |
+
+
+ | AWS_SHARED_CREDENTIALS_FILE |
+ Path to the AWS secret credentials. |
+ Default: /tmp/cloud_config.yml. For more information, go to AWS shared credentials file. |
+
+
+ | SEQUENCE |
+ Sequence of chaos execution for multiple instances. |
+ Default: parallel. Supports serial and parallel. For more information, go to sequence of chaos execution. |
+
+
+ | RAMP_TIME |
+ Period to wait before and after injecting chaos (in seconds). |
+ Optional. For more information, go to ramp time. |
+
+
+
+
+#### Process IDs
+
+The `PROCESS_IDS` environment variable specifies the processes that you want to kill by their IDs on a Windows EC2 instance.
+
+[embedmd]:# (./static/manifests/windows-ec2-process-kill/process-ids.yaml yaml)
+```yaml
+---
+# Kills processes by IDs on a Windows EC2 instance
+apiVersion: litmuschaos.io/v1alpha1
+kind: ChaosEngine
+metadata:
+ name: windows-ec2-process-kill
+spec:
+ engineState: "active"
+ chaosServiceAccount: litmus-admin
+ experiments:
+ - name: windows-ec2-process-kill
+ spec:
+ components:
+ env:
+ - name: PROCESS_IDS
+ value: '1234,5678'
+```
+
+#### Process Names
+
+The `PROCESS_NAMES` environment variable specifies the processes that you want to kill by their Names on a Windows EC2 instance.
+
+[embedmd]:# (./static/manifests/windows-ec2-process-kill/process-names.yaml yaml)
+```yaml
+---
+# Kills processes by names on a Windows EC2 instance
+apiVersion: litmuschaos.io/v1alpha1
+kind: ChaosEngine
+metadata:
+ name: windows-ec2-process-kill
+spec:
+ engineState: "active"
+ chaosServiceAccount: litmus-admin
+ experiments:
+ - name: windows-ec2-process-kill
+ spec:
+ components:
+ env:
+ - name: PROCESS_NAMES
+ value: 'notepad,explorer'
+```
+
+#### Force
+
+The `FORCE` environment variable specifies the force kill of the processes under chaos.
+
+
+[embedmd]:# (./static/manifests/windows-ec2-process-kill/force.yaml yaml)
+```yaml
+---
+# Kills processes by names with FORCE enabled on a Windows EC2 instance
+apiVersion: litmuschaos.io/v1alpha1
+kind: ChaosEngine
+metadata:
+ name: windows-ec2-process-kill
+spec:
+ engineState: "active"
+ chaosServiceAccount: litmus-admin
+ experiments:
+ - name: windows-ec2-process-kill
+ spec:
+ components:
+ env:
+ - name: PROCESS_NAMES
+ value: 'notepad'
+ - name: FORCE
+ value: 'enable'
+```
\ No newline at end of file
diff --git a/docs/chaos-engineering/faults/chaos-faults/kubernetes/experiments.ts b/docs/chaos-engineering/faults/chaos-faults/kubernetes/experiments.ts
index 053bfdbdffe..e04d09353f0 100644
--- a/docs/chaos-engineering/faults/chaos-faults/kubernetes/experiments.ts
+++ b/docs/chaos-engineering/faults/chaos-faults/kubernetes/experiments.ts
@@ -343,4 +343,16 @@ export const experiments: ExperimentDetails[] = [
tags: ["pod"],
category: "kubernetes",
},
+ {
+ name: "Pod Application Function Error",
+ description: "Pod Application Function Error injects an error into a specified function of an application running in a Kubernetes pod. This fault is useful for testing the resilience of your application to function-level errors.",
+ tags: ["pod", "function", "error"],
+ category: "kubernetes",
+ },
+ {
+ name: "Pod Application Function Latency",
+ description: "Pod Application Function Latency injects latency into a specified function of an application running in a Kubernetes pod. This fault is useful for testing the resilience of your application to function-level delays.",
+ tags: ["pod", "function", "latency"],
+ category: "kubernetes",
+ },
];
diff --git a/docs/chaos-engineering/faults/chaos-faults/kubernetes/kubernetes.md b/docs/chaos-engineering/faults/chaos-faults/kubernetes/kubernetes.md
index 2826e2780d5..26898f923c1 100644
--- a/docs/chaos-engineering/faults/chaos-faults/kubernetes/kubernetes.md
+++ b/docs/chaos-engineering/faults/chaos-faults/kubernetes/kubernetes.md
@@ -925,3 +925,37 @@ It can test the application's resilience for invalid system time.
+
+