Hey all 👋 Lately we’ve upgraded to flytekit 1.5.0 in order to use to associate pods templates to specific tasks, so we’ve deployed new PodTemplates with specific names (name under

metadata.name

) and assigned them as

pod_template_name=<name_of_PodTemplate>

- but it does not seem to apply the specific PodTemplate but still using the default one (still have the labels and fields of the default and not the specific one) Any idea why? (No logs in flyte-admin/propeller that mention the

pod_template_name

)

Did you upgrade the backend

Backend is at v1.1.40, haven’t seen anything in the changelog that could be affecting the pod_template since

I think this was definitely added after 1.1

Hi @boundless-answer-77411! Podtemplate backend comes after 1.1.63 (https://github.com/flyteorg/flytepropeller/pull/516). You can see more info under this ticket https://github.com/flyteorg/flyte/issues/3123

ohh perfect! could’t find it myself Thank you fellas 😄

No problem 🙂

hey, sorry for the bother we’ve updated to admin v1.1.71 and propeller 1.1.63 but still seems to not use the pod_template_name, no logs mention the pod_template_name either 😕 is there any other version or any clue where I can look to debug this further?

It’s not just propeller all backend needs to be updated

also updated the admin, scheduler and console

So 1.2 is a platform version

We could consider add some logs in flytepropeller, manually build propeller, and replace the propeller image

Why?

Typo. *you can consider

I think we should have bigger release notes. One idea is what we are working on - mono repo

In order to debug yourself

Just propeller won’t work. Admin has to be updated

I’ll try tomorrow to change to 1.2, but out of curiosity - updating both propeller and admin should work?

i do think so. feel free to reach out if you have any q. Also down for a chat or smth

Will do, thank you so much for the help! Going to try tomorrow updating both and see if it’ll work