| Kubelet service kill | Kubelet service kill makes the application unreachable on the account of the node turning unschedulable (NotReady). | node | #kubelet-service-kill |
| Node CPU hog | Node CPU hog exhausts the CPU resources on a Kubernetes node. | node | #node-cpu-hog |
| Node drain | Node drain drains the node of all its resources running on it. | node | #node-drain |
| Node IO stress | Node IO stress causes I/O stress on the Kubernetes node. | node | #node-io-stress |
| Node memory hog | Node memory hog causes memory resource exhaustion on the Kubernetes node. | node | #node-memory-hog |
| Node network latency | Node network latency introduces network latency to the Kubernetes node. | node | #node-network-latency |
| Node network loss | Node network loss introduces packet loss in the Kubernetes node. | node | #node-network-loss |
| Node restart | Node restart disrupts the state of the node by restarting it. | node | #node-restart |
| Node taint | Node taint taints (contaminates) the node by applying the desired effect. | node | #node-taint |
| Container kill | Container kill terminates a single container inside a target pod, leaving the pod scheduled so the container restarts in place. | pod | #container-kill |
| Disk fill | Disk fill consumes a configurable percentage of a target container's ephemeral storage to test eviction and write-failure handling. | pod | #disk-fill |
| FS fill | FS fill writes a configurable amount of data into a specific path inside a target container to test mounted-volume capacity and write-failure handling. | pod | #fs-fill |
| Pod API block | Pod API block drops selected API requests or responses on a target pod using path, method, header, query, and source or destination filters (with HTTPS support). | pod | #pod-api-block |
| Pod API latency | Pod API latency adds a configurable delay to selected API calls on a target pod with path, method, header, query, and source or destination filters (with HTTPS support). | pod | #pod-api-latency |
| Pod API modify body | Pod API modify body overwrites request or response bodies on selected API calls of a target pod using path, method, header, query, and source or destination filters (with HTTPS support). | pod | #pod-api-modify-body |
| Pod API modify header | Pod API modify header overrides request or response headers on selected API calls of a target pod using path, method, query, and source or destination filters (with HTTPS support). | pod | #pod-api-modify-header |
| Pod API status code | Pod API status code overrides the HTTP status code returned by selected API calls of a target pod using path, method, header, query, and source or destination filters (with HTTPS support). | pod | #pod-api-status-code |
| Pod API modify response custom | Pod API modify response custom combines status code, header, and body modifications on selected API calls of a target pod in a single experiment (with HTTPS support). | pod | #pod-api-modify-response-custom |
| Pod autoscaler | Pod autoscaler scales a target Deployment or StatefulSet to a configured replica count for a fixed duration to test cluster capacity and node autoscaling. | pod | #pod-autoscaler |
| Pod CPU hog | Pod CPU hog consumes excess CPU resources of the application container. | pod | #pod-cpu-hog |
| Pod delete | Pod delete removes one or more pods of a target workload to test replica availability, controller recovery, and graceful termination. | pod | #pod-delete |
| Pod DNS error | Pod DNS error fails DNS lookups from inside a target pod for selected hostnames (or all hostnames) to test how the application handles upstream lookup failures. | pod | #pod-dns-error |
| Pod DNS spoof | Pod DNS spoof redirects DNS lookups for selected hostnames inside a target pod to a different address so the application opens connections to the wrong destination. | pod | #pod-dns-spoof |
| Pod HTTP latency | Pod HTTP latency adds a configurable delay to HTTP responses served by a target pod on a chosen service port to test client timeouts, retries, and tail-latency budgets. | pod | #pod-http-latency |
| Pod HTTP modify body | Pod HTTP modify body overwrites the HTTP response body served by a target pod to test client behavior under corrupted, empty, or unexpected payloads. | pod | #pod-http-modify-body |
| Pod HTTP modify header | Pod HTTP modify header overrides HTTP request or response headers on a target pod to test resilience to missing, altered, or unexpected header values. | pod | #pod-http-modify-header |
| Pod HTTP reset peer | Pod HTTP reset peer forcibly resets TCP connections carrying HTTP requests to a target pod after a configurable delay to test client retry, connection-pool, and circuit-breaker behavior. | pod | #pod-http-reset-peer |
| Pod HTTP status code | Pod HTTP status code overrides the HTTP response status code returned by a target pod (and optionally overwrites the body) to test client error handling on specific HTTP statuses. | pod | #pod-http-status-code |
| Pod IO attribute override | Pod IO attribute override rewrites file attributes returned by stat syscalls on a target container's mounted volume to test how the application reacts to changed permissions, ownership, size, or timestamps. | pod | #pod-io-attribute-override |
| Pod IO error | Pod IO error makes filesystem syscalls on a target container's mounted volume return a configurable error code so you can validate how the application handles failed reads, writes, and opens. | pod | #pod-io-error |
| Pod IO latency | Pod IO latency adds a configurable delay to filesystem syscalls against a target container's mounted volume so you can test how the application behaves under slow storage. | pod | #pod-io-latency |
| Pod IO mistake | Pod IO mistake seeds wrong bytes into reads or writes against a target container's mounted volume so you can validate how the application detects and recovers from silent data corruption. | pod | #pod-io-mistake |
| Pod IO stress | Pod IO stress generates sustained filesystem read and write load inside a target container's mounted volume to test disk pressure, slow IO, and ephemeral-storage exhaustion. | pod | #pod-io-stress |
| Pod JVM method exception | Pod JVM method exception causes a specific Java method in a target JVM to throw a configurable exception on every invocation so you can test how callers handle the failure. | pod, jvm, exception | #pod-jvm-method-exception |
| Pod JVM CPU stress | Pod JVM CPU stress drives a configurable number of CPU cores inside a target JVM to test how the application behaves when its Java process is starved of CPU. | pod, jvm, cpu | #pod-jvm-cpu-stress |
| Pod JVM memory stress | Pod JVM memory stress injects JVM memory stress for a Java process executing in a Kubernetes pod by consuming excessive memory resources of the JVM. | pod, jvm, memory | #pod-jvm-memory-stress |
| Pod JVM modify return | Pod JVM modify return overrides the return value of a specific Java method in a target JVM so you can test how callers behave when a method silently returns wrong data. | pod, jvm | #pod-jvm-modify-return |
| Pod JVM Solace Latency | Pod JVM Solace Latency adds a configurable delay to Solace publisher or subscriber calls from a target JVM, scoped by topic or queue, to test timeout and back-pressure behavior under slow Solace messaging. | pod, jvm, solace, latency | #pod-jvm-solace-latency |
| Pod JVM Solace Exception | Pod JVM Solace Exception causes Solace publisher or subscriber calls from a target JVM to throw a configurable exception on a chosen topic or queue so you can test caller error handling. | pod, jvm, solace, exception | #pod-jvm-solace-exception |
| Pod JVM method latency | Pod JVM method latency adds a configurable delay to every invocation of a specific Java method in a target JVM so you can test how callers and dependents behave under slow methods. | pod, latency | #pod-jvm-method-latency |
| Pod JVM trigger gc | Pod JVM trigger gc forces an immediate full garbage collection in a target JVM so you can measure GC pause impact on latency, throughput, and downstream timeouts. | pod, jvm | #pod-jvm-trigger-gc |
| Pod JVM SQL Exception | Pod JVM SQL Exception causes JDBC calls from a target JVM to throw a configurable exception, scoped by table and SQL operation, so you can test how the application handles database failures. | pod, jvm, sql, exception | #pod-jvm-sql-exception |
| Pod JVM SQL Latency | Pod JVM SQL Latency adds a configurable delay to JDBC calls from a target JVM, scoped by table and SQL operation, so you can test connection-pool exhaustion and timeout handling under slow databases. | pod, jvm, sql, latency | #pod-jvm-sql-latency |
| Pod JVM Mongo Exception | Pod JVM Mongo Exception causes MongoDB calls from a target JVM to throw a configurable exception, scoped by database and collection, so you can test how the application handles MongoDB failures. | pod, jvm, mongo, exception | #pod-jvm-mongo-exception |
| Pod JVM Mongo Latency | Pod JVM Mongo Latency adds a configurable delay to MongoDB calls from a target JVM, scoped by database and collection, so you can test how the application behaves under slow MongoDB operations. | pod, jvm, mongo, latency | #pod-jvm-mongo-latency |
| Pod JVM Kafka Exception | Pod JVM Kafka Exception causes Kafka producer or consumer calls from a target JVM to throw a configurable exception on a chosen topic so you can test how the application handles Kafka failures. | pod, jvm, kafka, exception | #pod-jvm-kafka-exception |
| Pod JVM Kafka Latency | Pod JVM Kafka Latency adds a configurable delay to Kafka producer or consumer calls from a target JVM on a chosen topic so you can test how the application behaves under slow Kafka messaging. | pod, jvm, kafka, latency | #pod-jvm-kafka-latency |
| Pod memory hog | Pod memory hog consumes memory resources in excess, resulting in a significant spike in the memory usage of a pod. | pod | #pod-memory-hog |
| Pod network corruption | Pod network corruption flips random bits in a configurable percentage of packets on a target container's network path. | pod | #pod-network-corruption |
| Pod network duplication | Pod network duplication injects chaos to disrupt the network connectivity to Kubernetes pods. | pod | #pod-network-duplication |
| Pod network latency | Pod network latency adds a configurable delay to packets on a target container's network path. | pod | #pod-network-latency |
| Pod network loss | Pod network loss drops a configurable percentage of packets on a target container's network path. | pod | #pod-network-loss |
| Pod network partition | Pod network partition blocks 100% ingress and egress traffic of the target application by creating network policy. | pod | #pod-network-partition |
| Pod network rate limit | Pod network rate limit fault generates Traffic Control (tc) rules with Token Bucket Filter (TBF) to assess Kubernetes pod resilience under limited network bandwidth condition. | pod | #pod-network-rate-limit |
| Redis cache penetration | Redis cache penetration issues a configurable burst of reads for keys that do not exist against a target Redis instance to test downstream database load and null-cache protection. | pod, redis, cache | #redis-cache-penetration |
| Redis cache expire | Redis cache expire expires a configurable set of keys (or all keys) on a target Redis instance to test cold-cache resilience, refill behavior, and downstream database back-pressure. | pod, redis, expire | #redis-cache-expire |
| Redis cache limit | Redis cache limit caps the maximum memory of a target Redis instance to force evictions and out-of-memory write errors, then restores the original limit when the fault ends. | pod, cache, redis | #redis-cache-limit |
| Time chaos | Time chaos shifts the wall-clock or monotonic time observed by selected processes inside a target container to test application behavior under clock skew, token expiry, and time-based scheduling errors. | pod | #time-chaos |
| Pod Application Function Error | Pod Application Function Error makes a specific instrumented application function return a configurable error on a chosen percentage of invocations so you can test caller error handling and recovery. | pod, function, error | #pod-application-function-error |
| Pod Application Function Latency | Pod Application Function Latency adds a configurable delay to invocations of a specific instrumented application function so you can test how callers and dependents behave under slow functions. | pod, function, latency | #pod-application-function-latency |
| Pod Application Function Exception | Pod Application Function Exception throws a configurable exception from a specific instrumented application function so you can test how callers and dependents handle thrown failures, including retry filters and circuit breakers. | pod, function, exception | #pod-application-function-exception |