Add resources field to initContainer in TestRun CRD

[gcaldasnu]

Feature Description

Add the resource field to the initContainer within the TestRun Custom Resource Definition (CRD). This would allow users to explicitly configure CPU and memory requests and limits, ensuring that the initContainer is scheduled and runs stably.

Suggested Solution (optional)

apiVersion: k6.io/v1alpha1
kind: TestRun
metadata:
  name: my-test
spec:
  # ... other fields
  runner:
    initContainers:
      - name: example
        image: "busybox"
        resources:
          requests:
            memory: "64Mi"
            cpu: "100m"
          limits:
            memory: "128Mi"
            cpu: "200m"
  # ... other fields

Already existing or connected issues / PRs (optional)

#652

[yorugac]

Hi @gcaldasnu, thanks for the issue! I'm a bit confused here: we don't have .spec.sidecars in the TestRun CRD. Init containers are set via pod config like .spec.runner.initContainers. But looking at your PR, it seems that's what you meant? I.e. just extending the existing init containers.

Also, could you please describe your use case? For example, could you share what your init container is doing? I think we didn't have this request before so I'd assume usually, folk are not doing anything too heavy with the init containers 🙂

[gcaldasnu]

@yorugac You are right! Sorry, I corrected my example.
To answer your question, my scenario is as follows: I'm running a load test that uses an initContainer, which is responsible for preparing authentication for the main container. However, this initialization step is a cumbersome and time-consuming process, as it involves setting up a complex authentication environment.