Allow the K6 CRD to set environment variables for the runners. about k6-operator

[mikaelkundert]

I noticed that error message was about missing test.js, but here's the actual error message that indicates that latter command should work.

$ K6_STATSD_ADDR=graphite-1622816495:8125 k6 run --quiet --execution-segment=0:1/4 --execution-segment-sequence=0,1/4,2/4,3/4,1 -e K6_STATSD_ADDR=graphite-1622816495:8125 --out statsd ./test.js --address=0.0.0.0:6565 --paused

          /\      |‾‾| /‾‾/   /‾‾/   
     /\  /  \     |  |/  /   /  /    
    /  \/    \    |     (   /   ‾‾\  
   /          \   |  |\  \ |  (‾)  | 
  / __________ \  |__| \__\ \_____/ .io

ERRO[0000] Couldn't make buffered client, lookup graphite-1622816495 on 127.0.0.53:53: server misbehaving  output=statsd
ERRO[0000] lookup graphite-1622816495 on 127.0.0.53:53: server misbehaving 

[mikaelkundert]

Command seems to be assembled by jobs.NewRunnerJob at https://github.com/k6io/operator/blob/main/pkg/resources/jobs/runner.go#L24L115.

My initial vision for how to specify those environment variables would be using familiar env pattern such as:

apiVersion: k6.io/v1alpha1
kind: K6
metadata:
  name: k6-sample
spec:
  parallelism: 4
  script: crocodile-stress-test
  env:
    - name: K6_STATSD_ADDR
      value: graphite-1622816495:8125
  arguments: --out statsd

[simskij]

Yes, that would be my suggestion as well!