@Marvin Work pools have a setting for ImagePullPolicy, Workers can also have their ImagePullPolicy set via the helm chart, which one takes precedence?

It seems there's no explicit documentation or issues directly addressing the precedence of

ImagePullPolicy

between work pools and workers set via the Helm chart. Based on general practice in Kubernetes and similar systems, settings defined at a more specific level (e.g., worker level) typically override those at a broader level (e.g., work pool level). However, to get a definitive answer, I recommend checking the Prefect documentation on work pools or contacting the Prefect support team for clarification.

hey @Devin Bender - are you thinking of

--install-policy

on the worker? or where are you seeing image pull policy for the worker

I noticed you can define the pullpolicy directly on the worker via the helmchart, as shown in the templates in the screenshot

oh oh oh my bad

@Nate Ahh, the pod that is created when a flow starts?

yeah the helm chart's pull policy is about what image the worker (listener) pod uses when you install the chart and the work pool one is about the image pull policy for the pod when a flow run happens

Excellent @Nate thank you