[Feature]: PodSet Container to support Image and Command

[vsoch]

What you would like to be added?

Problem: If we want to manipulate a Container or InitContainer on the JobSet, e.g., here we need to expose the Image and Command for the InitContainer, which are generally needed. We cannot use PodSet for InitContainer without this exposure. The ultimate goal is to have the PodSet interface map onto the actual Jobset (e.g., PodSet -> runtime.Container -> JobSet) with changed Image and Command. Note that tests can then be refactored too (reference)

Why is this needed?

Customization of Image/Command for InitContainers is generally desired. For the Flux Policy PR/integration we are not able to use PodSet without it: #3064 (comment)

Love this feature?

Give it a 👍 We prioritize the features with most 👍

[andreyvelich]

After this PR is merged we need to pick this up. Context: #3064 (comment)

/remove-label lifecycle/needs-triage
/kind cleanup
/good-first-issue

[google-oss-prow]

@andreyvelich:
This request has been marked as suitable for new contributors.

Please ensure the request meets the requirements listed here.

If this request no longer meets these requirements, the label can be removed
by commenting with the /remove-good-first-issue command.

Details

In response to this:

After this PR is merged we need to pick this up. Context: #3064 (comment)

/remove-label lifecycle/needs-triage
/kind cleanup
/good-first-issue

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[Raakshass]

Hi @vsoch @andreyvelich, I'd like to work on this issue!

I'm already working on #3179 (FluxPolicy Testing) and this is directly related. I'll add Image and Command support to PodSet Container for InitContainer customization.

/assign

[vsoch]

That sounds great @Raakshass ! Thank you 🙏