kubeflow/trainer

[Feature]: PodSet Container to support Image and Command

Closed

#3,177 opened on Feb 5, 2026

 (12 comments) (0 reactions) (0 assignees)Go (964 forks)github user discovery
good first issuehelp wantedkind/cleanupkind/feature

Repository metrics

Stars
 (2,112 stars)
PR merge metrics
 (PR metrics pending)

Description

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: https://github.com/kubeflow/trainer/pull/3064#issuecomment-3815049315

Love this feature?

Give it a 👍 We prioritize the features with most 👍

Contributor guide