cuddly-jelly-27016
06/25/2025, 7:32 AMpod_template should be used for a given pod during run time. this is to allow let's say users to choose an AWS EC2 instance type, which associated to a managednodegroup in my EKS cluster
i saw in this PR, i am assuming flytekit>=1.15 onwards will have support for with_overrides method to override task's pod_template at runtime?
however, in my testing with flytekit=1.15.4, pod that is spun up in my flyte workflow always fails to be configured with the correct pod_template that is pass to the with_overrides method
i am wondering if this is a bug, or a gap in understanding of how the with_overrides(pod_template) feature works? because intuitively I expect this type of use case should be one of the primary reason for the introduction of this feature.
### Expected behavior
say i have this flyte workflow, pod_b always fail to spin up with the appropriate pod_template, regardless if task pod_b has the compile time podtemplates defined or NOT.
i expect that if i launch a flyte workflow execution with a selected pod_template, it would be able to spin up pod_b with the correct pod_template
@workflow
def wf_a(.., pod_template="a"):
pod_a(.., pod_template="a")
@dynamic
def pod_a(..., pod_template="a"):
pod_b(..).with_overrides(requests=.., limits=.., pod_template="a")
@task
def pod_b(..)
<other_logic>
### Additional context to reproduce
No response
### Screenshots
No response
### Are you sure this issue hasn't been raised already?
• Yes
### Have you read the Code of Conduct?
• Yes
flyteorg/flytecuddly-jelly-27016
06/25/2025, 7:32 AM