Consider imagePullPolicy for init containers #317

Merged
zeripath merged 2 commits from justusbunsi/helm-chart:enhancement/image-pull-policy into master 2022-04-21 22:13:19 +00:00

2 Commits

Author SHA1 Message Date
justusbunsi
9f835ac825 Merge branch 'master' into enhancement/image-pull-policy
All checks were successful
continuous-integration/drone/pr Build is passing
2022-04-22 03:06:10 +08:00
justusbunsi
104a32981c Consider imagePullPolicy for init containers
All checks were successful
continuous-integration/drone/pr Build is passing
The default behaviour for container image pulls depend on different values
such as image tag usage and its value.
See https://kubernetes.io/docs/concepts/containers/images/#imagepullpolicy-defaulting

It leads to an unintended behaviour for this Helm Chart. Kubernetes
will always pull the image for init containers when using the `latest`
Gitea image, even if `Values.image.pullPolicy` defines a different value
for the runtime container.
2022-04-21 11:10:18 +02:00