<#6530 Fix PodTemplate resource state pollution be...
# flyte-github
c
#6530 Fix PodTemplate resource state pollution between workflow runs Pull request opened by punkerpunker ## Tracking issue #6529 ## Why are the changes needed? Without that, in cases where
podTemplate
is involved we could get unexpected resource overrides from previous runs. ## What changes were proposed in this pull request? I changed LoadOrDefault() to return a deep copy of the cached pod template, this ensures that each workflow gets its own independent copy of the pod template, preventing any mutations from affecting other workflows ## How was this patch tested? I've tested it in the Flyte multi-cluster environment of ours (devel) ## Check all the applicable boxes • I updated the documentation accordingly. • All new and existing tests passed. • All commits are signed-off. ## Related PRs This is a follow-up for #6483 https://bito.ai#summarystart| ### Summary by Bito This pull request resolves resource state pollution in PodTemplate management within the Flyte framework by ensuring each workflow has an independent PodTemplate copy. This change is vital for preserving workflow execution integrity, particularly in multi-cluster setups. flyteorg/flyte