k6-operator
k6-operator copied to clipboard
An operator for running distributed k6 tests.
### Brief summary I installed the operator as described in the README using the bundle (https://github.com/grafana/k6-operator?tab=readme-ov-file#bundle-deployment). I am able to run a test, but when the TestRun resource is deleted...
As part of my specific deployment, I needed to add the system environment variables into the Initializer Job.
### Feature Description My current deployment requires to do vpn connections which are done by executing a process in the background e.g. `./scripts/vpn &`. If I don't execute it in...
### Feature Description The current `TestRun` resource cleans up resources used for the load test through the cleanup property. However, there is a need to be able to debug failed...
Issue: https://github.com/grafana/k6-operator/issues/398
Historically, k6-operator has been quite a straight-forward project (as far as Kubernetes operators go) and pretty straight-forward to maintain or to work with. But recently, it has been becoming more...
### Feature Description Currently, `resources` for PrivateLoadZone test runs are set only during creation of PLZ as part of its spec. To change them, one has to delete and re-create...
`buildx` version in `docker/setup-buildx-action` GA was pinned for a year since this commit: https://github.com/grafana/k6-operator/commit/d0005208fdff2eaaa6a967ca739ba5b91c868552 The reason: Docker manifests being broken for some k8s setups. This issue was raised in `setup-buildx-action`...
### Brief summary The documentation in [step 4 on the procedure on this page](https://grafana.com/docs/grafana-cloud/k6/author-run/private-load-zone-v2/#create-the-plz-crd) says the following about the PLZ resources > Note that currently, resources can only be configured...
### Brief summary Hello Team. We only started to use K6 Operator in our environment. But we have an issue with Initializer, it fails on --execution-requirements if we have in...