[BUG] Namespace creation fails with default pod template about flyte

[welcome]

Thank you for opening your first issue here! 🛠

[runllm]

The issue you're experiencing seems related to the configuration and namespace handling of PodTemplates in Flyte. According to this discussion, PodTemplates need to be present in the namespace where the execution is triggered. Additionally, another discussion mentions that PodTemplates are namespace-specific and should be configured accordingly. Lastly, this issue highlights that the default-pod-template-name should be correctly set in the FlytePropeller configuration.

Would you like more details on how to configure the namespaces and PodTemplates correctly?

Sources:

• Facing below error while trying to use podTemplate for a TfJob
• Hey question about podtemplates I ve setup mine by adding it
• I m having an issue with setting default pod template name

---

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!

[davidmirror-ops]

@nuhaj what version of Flyte are you using?
@hamersaw is this the PR that freed the watch from having to have the default Pod template set? flyteorg/flytepropeller#614

[nuhaj]

flyte-binary-release:v1.12.0

[hamersaw]

@nuhaj what version of Flyte are you using?
@hamersaw is this the PR that freed the watch from having to have the default Pod template set? flyteorg/flytepropeller#614

Yes, this looks like it.