Assigning runner's security context to k6 initializer

[mohamediag]

Feature Description

We would need to define securityContext on all pods created by K6 operator as per security requirement , but currently the initializer doesn't provide an option to do it.

Suggested Solution (optional)

No response

Already existing or connected issues / PRs (optional)

No response

[yorugac]

Hi @mohamediag, thanks for opening the issue! One way to resolve this is in the PR #175 - with it, you should be able to explicitly specify initializer spec separately from the runner.

But it might also be good to consider adding security context assigned in initializer definition by default: similarly to how its done in the runner definition.

[mohamediag]

Hi @yorugac , seems the first PR is not being looked for a while, therefore the second option is fine for me as it seems quick to implement.

Shall a raise a PR for it if the repo is open for external contributor or can someone do it?

[yorugac]

Please feel free to work on the PR with assigning runner's security context to initializer @mohamediag 🙂 It doesn't contradict PR #175 but complements it so it'd be good to have it anyway.

[mohamediag]

PR opened : #215

[mohamediag]

Hi @yorugac any idea when the PR can be reviewed and merged?

[yorugac]

Closed by #215