From 191b8cb0ec0a06b209c47d4001a65a5639f79077 Mon Sep 17 00:00:00 2001 From: Miguel Duarte Barroso Date: Wed, 26 Jan 2022 13:37:03 +0100 Subject: [PATCH] e2e tests: always pull new multus images (#783) Currently, the local workflow is far from optimal, since for every change on the multus images the developers are required to redeploy the kind cluster. A more efficient workflow would be to build a local image, upload it to the kind cluster, and finally re-deploy (delete & re-provision) the daemonset, which would be running the new version. For this flow to be possible, the multus container `imagePullPolicy` must be set to `Always` - [0] - otherwise, the image is not updated. [0] - https://kubernetes.io/docs/concepts/containers/images/#updating-images Signed-off-by: Miguel Duarte Barroso --- e2e/multus-daemonset.yml | 1 + 1 file changed, 1 insertion(+) diff --git a/e2e/multus-daemonset.yml b/e2e/multus-daemonset.yml index 9b93bd95..0dfa2d44 100644 --- a/e2e/multus-daemonset.yml +++ b/e2e/multus-daemonset.yml @@ -154,6 +154,7 @@ spec: containers: - name: kube-multus image: localhost:5000/multus:e2e + imagePullPolicy: Always command: [ "/usr/src/multus-cni/bin/multus-daemon" ] args: - "-multus-conf-file=auto"