b06b3edf1d
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. Reviewed-on: https://gitea.com/gitea/helm-chart/pulls/317 Reviewed-by: techknowlogick <techknowlogick@gitea.io> Reviewed-by: Gusted <williamzijl7@hotmail.com> Co-authored-by: justusbunsi <justusbunsi@noreply.gitea.io> Co-committed-by: justusbunsi <justusbunsi@noreply.gitea.io> |
||
|---|---|---|
| .. | ||
| config.yaml | ||
| deprecation.yaml | ||
| http-svc.yaml | ||
| ingress.yaml | ||
| init.yaml | ||
| servicemonitor.yaml | ||
| ssh-svc.yaml | ||
| statefulset.yaml | ||