Olha Yevtushenko

There were situations when adding new functionality to the operator broke previously supported use cases. This problem happens mostly due to two main reasons: - time limit: not enough grokking,...

We can also refer to these examples in the future docs "k6-operator section". Additionally consider if this folder should be renamed to `examples` or a new one added, etc.

Kubernetes components come with [metrics built-in](https://kubernetes.io/docs/concepts/cluster-administration/system-metrics/), more or less, so the operator should try to follow the same principle. One goal is to monitor what tests are being run via...

This is an umbrella issue to improve networking in the operator. Currently, details are best described here: https://github.com/grafana/k6-operator/pull/146#issuecomment-1351766577 And also PR for IPv6: https://github.com/grafana/k6-operator/issues/171 It's best to address these points...

HTTP call to terminate k6 process

7

### Feature Description Currently there is a [Stop test](https://grafana.com/docs/k6/latest/misc/k6-rest-api/#stop-test) HTTP call which allows to stop the test itself but does not terminate the k6 process. This is easily noticeable when...

Defining thresholds in `setup`

1

### Feature Description Currently [thresholds](https://k6.io/docs/using-k6/thresholds/) can be defined only in init context, as part of `options` const object. This has its limitations: if threshold must depend on a value unavailable...

Issue: https://github.com/grafana/k6-operator/issues/398

Refactor `TestRun` controller

1

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...