Olha Yevtushenko

Make the operator idempotent

1

This is an umbrella issue for WIP investigation that is being done to resolve the problems mentioned below. There are two major issues in the k6 Operator that came up...

The test run with cloud output is not resilient towards external restart of operator's pod. This happens mainly due to the controller not storing its full state with cloud output...

Cloud output is being added to k6-operator in #86 and this feature requires an authorization token to be loaded and passed to the pods. Currently, this is implemented with Kubernetes...

Users of k6-operator can face migration issues where they need to re-configure both their setups and k6 scripts to distributed execution. Currently it's fully user's responsibility but a straight-forward guide...

Check and confirm the installation and execution on Windows

9

Currently k6-operator has only a tutorial in [blog post](https://k6.io/blog/running-distributed-tests-on-k8s/) and a README for options. It has been suggested that a quick, step-by-step guide could be of use too. Also to...

Design and implement a config for distributed execution setup

3

Currently k6-operator supports only the simplest straight-forward distributed setup when 100% of execution is spread in equal chunks `100% / N` to `N` runners. But k6 is far more versatile...

Remove starter job in favor of built-in implementation

11

## Problem The starter is currently relying on REST API of k6 to start the runners. It is a workable solution that allows to synchronize the start of the test....

Investigate potential switch of the logging library

3

k6-operator is using logr while k6 is using logrus. This results in k6-operator using 2 logging libs at once since https://github.com/grafana/k6-operator/pull/86. Consider switching to logrus in k6-operator or perhaps using...

Currently unit tests in the operator have a simple test function per test case which results in a lot of hard-coding. Also, the coverage is not ideal. Look into possible...

Currently, k6-operator with `ConfigMap` and `VolumeClaim` options expects JS script to be present in `/test` folder: https://github.com/grafana/k6-operator/blob/de5794766160bca70dfb8a06e6868b0ae8aa2c86/pkg/types/types.go#L22-L57 These two options don't match how `LocalFile` is implemented and it also [causes...