Addon init containers: imagePullPolicy=Always so rebuilt images under same tag are picked up

This commit is contained in:
Tower Deploy
2026-04-27 12:38:10 +03:00
parent 9546a243f7
commit 32869f74e8

View File

@@ -34,11 +34,20 @@ spec:
# which is the shared volume the Odoo container reads from. # which is the shared volume the Odoo container reads from.
# Init containers run in order, but each writes to its own # Init containers run in order, but each writes to its own
# subdir, so order doesn't matter. # subdir, so order doesn't matter.
#
# `imagePullPolicy: Always` is intentional: addon images can be
# rebuilt under the same {code}:{version} tag (e.g. when Tower's
# build pipeline changes — adding pip-install layer for python
# external_dependencies). With IfNotPresent, kubelet would
# reuse the cached old digest and the pod would never see the
# new content. Always forces a manifest fetch on each pod
# start; layers themselves are still cached so the pull is
# cheap (~50 ms when content is unchanged, fresh otherwise).
initContainers: initContainers:
{{- range $i, $a := .Values.addons }} {{- range $i, $a := .Values.addons }}
- name: addon-{{ $a.code | replace "_" "-" | lower }} - name: addon-{{ $a.code | replace "_" "-" | lower }}
image: {{ $a.image }}:{{ $a.version }} image: {{ $a.image }}:{{ $a.version }}
imagePullPolicy: IfNotPresent imagePullPolicy: Always
volumeMounts: volumeMounts:
- name: addons - name: addons
mountPath: /target mountPath: /target