[BUG] regression: envFrom provided from pod template is discarded

[flixr]

Describe the bug

In flyte 1.11 setting a EnvFromSource via pod template works, but this broke with #4969

I have a pod template something like:

primary_container = V1Container(name="primary")
primary_container.env_from = [V1EnvFromSource(secret_ref=V1SecretEnvSource(name="my-secret"))]
ps = V1PodSpec(containers=[primary_container])
pod_template = PodTemplate(pod_spec=ps, primary_container_name="primary")

Expected behavior

The env variables loaded from my-secret are injected into the pod as specified in the pod template.

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

[runllm]

The issue you're describing seems to be related to a regression introduced by a recent pull request. The envFrom provided in the pod template is not being respected in the latest Flyte version. This was working in Flyte 1.11 but broke after the changes in PR #4969.

Would you like more details on how to potentially work around this issue or further steps to debug it?

Sources:

• Namespaces for pods and projects
• Hello I m trying to pass certain variables to my Flyte worke
• Hey team Hope you re doing okay slightly smiling face I ve g
• PR #4969

---

This is an AI-generated response and your feedback is appreciated! Please leave a 👍 if this is helpful and 👎 if it is not.

Mention @RunLLM to ask follow-up questions. See runllm.com for more!