mirror of
https://github.com/helm/charts.git
synced 2026-08-23 22:37:45 +00:00
[stable/jasperreports] Use immutable tags (#14214)
* Bump chart version Signed-off-by: Carlos Rodriguez Hernandez <crhernandez@bitnami.com> * [stable/jasperreports] Use immutable tags Signed-off-by: Carlos Rodriguez Hernandez <crhernandez@bitnami.com>
This commit is contained in:
committed by
Kubernetes Prow Robot
parent
c049b66562
commit
c7299a6210
@@ -1,6 +1,6 @@
|
||||
apiVersion: v1
|
||||
name: jasperreports
|
||||
version: 4.2.1
|
||||
version: 4.2.2
|
||||
appVersion: 7.2.0
|
||||
description: The JasperReports server can be used as a stand-alone or embedded reporting
|
||||
and BI server that offers web-based reporting, analytic tools and visualization,
|
||||
|
||||
@@ -53,7 +53,7 @@ The following table lists the configurable parameters of the JasperReports chart
|
||||
| `global.imagePullSecrets` | Global Docker registry secret names as an array | `[]` (does not add image pull secrets to deployed pods) |
|
||||
| `image.registry` | JasperReports image registry | `docker.io` |
|
||||
| `image.repository` | JasperReports Image name | `bitnami/jasperreports` |
|
||||
| `image.tag` | JasperReports Image tag | `{VERSION}` |
|
||||
| `image.tag` | JasperReports 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) |
|
||||
| `jasperreportsUsername` | User of the application | `user` |
|
||||
@@ -117,6 +117,12 @@ $ helm install --name my-release -f values.yaml stable/jasperreports
|
||||
|
||||
> **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 JasperReports](https://github.com/bitnami/bitnami-docker-jasperreports) image stores the JasperReports data and configurations at the `/bitnami/jasperreports` path of the container.
|
||||
|
||||
@@ -46,3 +46,10 @@ host. To configure JasperReports to use and external database host:
|
||||
helm upgrade {{ .Release.Name }} --set service.type={{ .Values.service.type }},mariadb.enabled=false,externalDatabase.host=YOUR_EXTERNAL_DATABASE_HOST stable/jasperreports
|
||||
|
||||
{{- 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 }}
|
||||
|
||||
@@ -13,7 +13,7 @@
|
||||
image:
|
||||
registry: docker.io
|
||||
repository: bitnami/jasperreports
|
||||
tag: 7.2.0
|
||||
tag: 7.2.0-debian-9-r5
|
||||
## 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
|
||||
|
||||
Reference in New Issue
Block a user