Feature request: can be set environment variable from envFrom in k6 CR.

[mugioka]

motivation

When executing k6 scripts, we need to handle sensitive information such as API Key in environment variables, but currently we cannot define environment variables in envFrom, so we are having trouble handling sensitive information.
By enabling envFrom to be used with k6 CR, secret information can be managed with secret resources, making it possible to handle secret information more securely.

[BarthV]

https://github.com/grafana/k6-operator/blob/main/api/v1alpha1/k6_types.go#L53-L65

K6 specs Runner key is (almost) a standard kubernetes pod spec, it includes standard []corev1.EnvVar spec for env specifications.
So you can perfectly add standard pod env specs usign any existing configMap or Secret.

An example from my own test suites :

apiVersion: k6.io/v1alpha1
kind: K6
metadata:
  name: k6
spec:
  parallelism: 2
  script:
    localFile: /k6/pipeline.js
  arguments: --stage 120s:180 --stage 300s:360 --stage 420s:360 --stage 60s:0
  runner:
    env:
    - name: FOOBAR
      value: http://foo.bar
    - name: SECRET
      valueFrom:
        secretKeyRef:
          name: my-api-secret
          key: secret
    - name: SOME_VAR
      value: any-value

[mugioka]

Ah, sure, but I think it would be better to be able to use envFrom if you want to handle multiple environment variables.

[yorugac]

I'm inclined to agree that env is sufficient in many cases, esp. since k6-operator is fully on-premise deployment anyway. So it seems like envFrom is more about convenience than anything else. But that's important too and I'll be happy to merge it as a PR. Thank you 😄

[deepikaUKG]

How do we access the env variable in K6 file. Unable to access as __ENV.myVar

[yorugac]

@deepikaUKG This is a closed issue 🙂 Please consult official k6 docs and community forum regarding env vars in k6 scripts. If the problem persists, feel free to open a new forum topic or, if you're certain its a bug, open a bug report on Github.