k6-operator
k6-operator copied to clipboard
grafana
An operator for running distributed k6 tests.
### Feature Description Unless there are plans to support other values and make it sort of an enum (which is also a breaking change), it probably makes more sense for...
**Summary** Bug Fixed: [Starter doesn't work in an IPv6 cluster](https://github.com/grafana/k6-operator/issues/171) This pull request addresses the IPv6 compatibility issue in the k6-operator as outlined in the referenced issue. Specifically, the changes...
By running two commands instead of one (the second being the cat | grep), any failures (non-zero exit code) of the first part (containing `k6 inspect`) will be lost and...
### Brief summary We realized, that our TestRuns get stuck without any information/logs printed out if the script itself is incorrect. # Cause We already had a deeper look and...
### Feature Description Currently `.spec.cleanup` in `TestRun` supports only one option, `"post"`. When set, it results in k6-operator cleaning up the CR and all its resources after the test run...
Use exit codes (of k6 archive + inspect) as sole indication for initialization success 1) Introduce an `EmptyDir` volume for temporary data This removes the need for any mkdir and...
### Feature Description k6-operator currently uses a public image hosted at our [ghcr](https://github.com/grafana/k6-operator/pkgs/container/k6-operator) as a default image for runners. This image is built from the [Dockerfile](https://github.com/grafana/k6-operator/blob/main/Dockerfile.runner) on each release of...
Distributed execution inevitably adds complexity and sometimes there is a need in additional information about how the workload is split between runners. Sample questions: - https://github.com/grafana/k6-operator/issues/120 - https://github.com/grafana/k6-operator/issues/209 It'd be...
Bumps: - Golang to 1.22 - controller-gen to 0.16.1 - controller-runtime to 0.19.0 Additionally, some cleaning up of Makefile.
### Feature Description Currently the operator works on all TestRun resources and moves them through the state machine - initialization - initialized - created - started - stopped - finished...