Error when run test on 500 pods

[volnyansky]

Brief summary

I'm trying to run the test on 500 pods and get the error : exec /usr/bin/k6: argument list too long
I find a workaround by batching tests in 300 pods packages with the same test id

k6-operator version or image

0.0.14

Helm chart version (if applicable)

k6-operator-3.6.0

TestRun / PrivateLoadZone YAML

apiVersion: k6.io/v1alpha1 kind: TestRun metadata: name: ${USERNAME}-${SCRIPT}-${BATCH} namespace: k6 spec: #number of pods to run in parallel parallelism: ${BATCH_PODS} script: configMap: name: ${USERNAME}-test-script-${BATCH} file: test.tar arguments: -o experimental-prometheus-rw --tag testid=${TESTID} runner: image: 569129334545.dkr.ecr.us-east-1.amazonaws.com/k6-robot-dev:latest env: - name: K6_PROMETHEUS_RW_SERVER_URL value: "http://victoria-metrics-single-server.monitoring.svc.cluster.local:8428/api/v1/write" - name: K6_PROMETHEUS_RW_TREND_STATS value: "count,sum,min,max,avg,med,p(90),p(95),p(99)" - name: K6_BROWSER_ARGS value: "window-size=1920x1080,no-sandbox,disable-setuid-sandbox,allow-file-access,use-fake-device-for-media-stream,use-fake-ui-for-media-stream,use-file-for-fake-video-capture=/usr/local/assets/video.mjpeg,use-file-for-fake-audio-capture=/usr/local/assets/audio.wav" - name: K6_BROWSER_TIMEOUT value: "45s" - name: VU_ID_START value: "${VU_ID_START}" nodeSelector: engageli.com/role: k6-load-test resources: limits: cpu: "${CPU}" memory: ${MEMORY}Mi requests: cpu: 100m memory: ${MEMORY}Mi

Other environment details (if applicable)

No response

Steps to reproduce the problem

Run test on 500pods , number of VUs doesn't matter

Expected behaviour

Tets runs in given number of pods

Actual behaviour

Test crashes