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

[pablochacin]

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 the xk6-disruptor-agent (see get started guide for more details).

One alternative is to install the k6-operator using a service account that has such permissions.

Document the issue and the solution using k6-operator, including the permissions required by the service account.

Requires:

• [x] https://github.com/grafana/xk6-disruptor/issues/78
• [x] https://github.com/grafana/xk6-disruptor/issues/96

[mcandeia]

@pablochacin qq: Why not use the in-cluster config instead ? I think it will be a matter of falling back to incluster whether none of this options are available, does this make sense?

[pablochacin]

Hi @mcandeia. I haven't tried but I think you are right, by allowing using the in-cluster config as you suggest, it should be possible to run the disruptor in the cluster as a Pod.

However, it would still be necessary to provide the test script for the disruptor and configure the k6 options for running it. This is what the operator does and is the reason we suggest using the operator for running tests in a cluster instead of launching your own pods.

I'm opening an issue for defaulting to the in-cluster config in the disruptor.