[stable/phabricator] Use immutable tags (#14202)

* Bump chart version

Signed-off-by: Carlos Rodriguez Hernandez <crhernandez@bitnami.com>

* [stable/phabricator] Use immutable tags

Signed-off-by: Carlos Rodriguez Hernandez <crhernandez@bitnami.com>
This commit is contained in:
Carlos Rodríguez Hernández
2019-05-28 09:39:56 -07:00
committed by Kubernetes Prow Robot
parent 00b59a0c0f
commit 8e9150e6f5
4 changed files with 16 additions and 3 deletions
+1 -1
View File
@@ -1,6 +1,6 @@
apiVersion: v1
name: phabricator
version: 4.2.8
version: 4.2.9
appVersion: 2019.20.0
description: Collection of open source web applications that help software companies build better software.
keywords:
+7 -1
View File
@@ -53,7 +53,7 @@ The following table lists the configurable parameters of the Phabricator chart a
| `global.imagePullSecrets` | Global Docker registry secret names as an array | `[]` (does not add image pull secrets to deployed pods) |
| `image.registry` | Phabricator image registry | `docker.io` |
| `image.repository` | Phabricator image name | `bitnami/phabricator` |
| `image.tag` | Phabricator image tag | `{VERSION}` |
| `image.tag` | Phabricator image tag | `{TAG_NAME}` |
| `image.pullPolicy` | Image pull policy | `Always` if `imageTag` is `latest`, else `IfNotPresent` |
| `image.pullSecrets` | Specify docker-registry secret names as an array | `[]` (does not add image pull secrets to deployed pods) |
| `phabricatorHost` | Phabricator host to create application URLs | `nil` |
@@ -141,6 +141,12 @@ $ helm install --name my-release -f values.yaml stable/phabricator
> **Tip**: You can use the default [values.yaml](values.yaml)
### [Rolling VS Immutable tags](https://docs.bitnami.com/containers/how-to/understand-rolling-tags-containers/)
It is strongly recommended to use immutable tags in a production environment. This ensures your deployment does not change automatically if the same tag is updated with a different image.
Bitnami will release a new chart updating its containers if a new version of the main container, significant changes, or critical vulnerabilities exist.
## Persistence
The [Bitnami Phabricator](https://github.com/bitnami/bitnami-docker-phabricator) image stores the Phabricator data and configurations at the `/bitnami/phabricator` and `/bitnami/apache` paths of the container.
+7
View File
@@ -48,3 +48,10 @@ host. To configure Phabricator with the URL of your service:
echo Username: {{ .Values.phabricatorUsername }}
echo Password: $(kubectl get secret --namespace {{ .Release.Namespace }} {{ template "phabricator.fullname" . }} -o jsonpath="{.data.phabricator-password}" | base64 --decode)
{{- end }}
{{- if and (contains "bitnami/" .Values.image.repository) (not (.Values.image.tag | regexFind "-r\\d+$")) }}
WARNING: Rolling tag detected ({{ .Values.image.repository }}:{{ .Values.image.tag }}), please note that it is strongly recommended to avoid using rolling tags in a production environment.
+info https://docs.bitnami.com/containers/how-to/understand-rolling-tags-containers/
{{- end }}
+1 -1
View File
@@ -13,7 +13,7 @@
image:
registry: docker.io
repository: bitnami/phabricator
tag: 2019.20.0
tag: 2019.20.0-debian-9-r12
## Specify a imagePullPolicy
## Defaults to 'Always' if image tag is 'latest', else set to 'IfNotPresent'
## ref: http://kubernetes.io/docs/user-guide/images/#pre-pulling-images