How do you change imagePullPolicy for existing deployments B

Question

How do you change imagePullPolicy for existing deployments By default its ifnotpresent but I would like to change it to always for all of my potential docker images containers Do I have to use <https kubernetes io docs reference access authn authz admission controllers alwayspullimages>

Ketan (kumare3) · Answer

use PodTemplate to adjust the policy

Kevin Su · Answer

Here is an <https docs flyte org en latest deployment cluster config general html id1|example>

Laura Lin · Answer

```kubectl apply f lt lt EOF apiVersion v1 kind PodTemplate metadata name flyte template namespace flyte template spec containers name default image <http docker io rwgrim docker noop|docker io rwgrim docker noop> imagePullPolicy Always EOF``` something like this is on the per container level right so I have to add one for each possible container I want to use

Kevin Su · Answer

yes

Laura Lin · Answer

I created a pod template named `flyte template` under the namespace `flyte` And then added it to the helm chart `kubectl get ConfigMap n flyte flyte propeller config o yaml` returns ```k8s yaml | plugins k8s default cpus 100m default env vars default memory 100Mi default pod template name flyte template``` but new task pods still have IfNotPresent when I view in `kubectl edit pod aflvhfnpb4hjb4rtxnnz fzmlagaq 0 n flytetester development o yaml` verified that the image in the task yaml is one that was specified as Always in the pod template

Laura Lin · Answer

Oh I don t think the pod template is being used at all because I added a new random label and I don t see it in new pods

Ketan (kumare3) · Answer

Cc < Dan Rammer hamersaw >

Dan Rammer (hamersaw) · Answer

Hi < Laura Lin> a few questions 1 what version of FlytePropeller are you running 2 What namespace if FlytePropeller running in

Laura Lin · Answer

is copilot required

Dan Rammer (hamersaw) · Answer

it should not be

Laura Lin · Answer

flytepropeller is running in flyte namespace how do I check the version this is what I see in the pod log ``` App flytepropeller Version unknown BuildSHA unknown BuildTS 2022 11 02 18 05 16 617334666 +0000 UTC m=+0 030357149 ```

Dan Rammer (hamersaw) · Answer

can you see what image is running in the Pod

Laura Lin · Answer

```Container image <http cr flyte org flyteorg flytepropeller release v1 2 0|cr flyte org flyteorg flytepropeller release v1 2 0> already present on machine```

Dan Rammer (hamersaw) · Answer

and what time did the container start

Laura Lin · Answer

8 minutes ago

Laura Lin · Answer

```<http helm sh chart|helm sh chart> flyte core v1 2 0```

Dan Rammer (hamersaw) · Answer

oh perfect laughing so it s not a stale version of propeller

Dan Rammer (hamersaw) · Answer

Can you try to create that same PodTemplate with the label test you were trying in the namespace that the Pod will be created in So in your test it looks like `flytetester development`

Laura Lin · Answer

did that too no difference

Dan Rammer (hamersaw) · Answer

OK I m diving into this and having trouble figuring out what could be going wrong Just to reclarify the Pod has been restarted since the configuration change right This isn t a configuration update the FlytePropeller can process while running

Laura Lin · Answer

the flytepropeller pods have been restarted since I updated the helm chart and I am kicking off new pods using flyte ui

Laura Lin · Answer

< Dan Rammer hamersaw > jumped on a call and helped turns out I wasn t setting the imagePullPolicy field under default primary container I was just adding it to new containers based on the images I was using

Laura Lin · Answer

thanks a lot for the help everyone pray