pablochacin

The documentation for the `injectHTTPFaults` methods for the [PodDisruptor](https://k6.io/docs/javascript-api/xk6-disruptor/api/poddisruptor/injecthttpfaults/) and [ServiceDisruptor](https://k6.io/docs/javascript-api/xk6-disruptor/api/servicedisruptor/injecthttpfaults/) do not explain these two methods' differences in treating the `port` parameter in the [httpFault](https://k6.io/docs/javascript-api/xk6-disruptor/api/faults/http/). The `PodDisruptor` interprets the...

The xk6-disruptor API is built around the concept of disruptors that inject faults. Presently, each disruptor implements one method for each type of fault it injects and different disruptors can...

Document how to run xk6-disruptor tests using the k6-operator

2

Is some setting, users may not be allow to run tests that use the xk6-disruptor, because the user lacks the permissions for running containers with the security privileges needed by...

Currently, the Kubernetes helper package's tests use to some extend helper functions provided by that same package for the test setup, creating a kind of circular dependency between the tests...

Presently the communication between the `xk6-disruptor` extension and the `xk6-disruptor-agent` running in the target Pods is implemented by executing a CLI command in the agent's container. This approach has several...

output format for errors changes to structured log when running k6 as a subprocess

4

### Brief summary When running k6 as a subprocess (from a go program) and capturing the stdout and stderr in a buffer, the format of error messages changes to a...

The functionality for building custom k6 binaries with extensions has been extracted and refactored in the github.com/grafana/k6foundry library. xk6 can be re-implemented using this library, leaving only the CLI interface...