Consider imagePullPolicy for init containers #317

Merged
justusbunsi merged 2 commits from refs/pull/317/head into master 2022-04-21 22:13:19 +00:00
justusbunsi commented 2022-04-21 09:12:40 +00:00 (Migrated from gitea.com)

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 tag, even if Values.image.pullPolicy defines a different
value for the runtime container.

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 tag, even if `Values.image.pullPolicy` defines a different value for the runtime container.
techknowlogick (Migrated from gitea.com) approved these changes 2022-04-21 15:51:41 +00:00
Gusted (Migrated from gitea.com) approved these changes 2022-04-21 20:05:27 +00:00
takirala (Migrated from gitea.com) approved these changes 2022-04-21 21:13:57 +00:00
Sign in to join this conversation.
No description provided.