[stable/jasperreports] Fix chart not being upgradable (helm#7818)

Signed-off-by: Javier J. Salmeron Garcia <jsalmeron@bitnami.com>
wgiddens · Jan 18, 2019 · 7691a71 · 7691a71
1 parent 4eceff5
commit 7691a71
Show file tree

Hide file tree

Showing 3 changed files with 16 additions and 1 deletion.
diff --git a/stable/jasperreports/Chart.yaml b/stable/jasperreports/Chart.yaml
@@ -1,5 +1,5 @@
 name: jasperreports
-version: 2.0.4
+version: 3.0.0
 appVersion: 7.1.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,

diff --git a/stable/jasperreports/README.md b/stable/jasperreports/README.md
@@ -105,3 +105,14 @@ The [Bitnami JasperReports](https://github.com/bitnami/bitnami-docker-jasperrepo
 
 Persistent Volume Claims are used to keep the data across deployments. This is known to work in GCE, AWS, and minikube.
 See the [Configuration](#configuration) section to configure the PVC or to disable persistence.
+
+## Upgrading
+
+### To 3.0.0
+
+Backwards compatibility is not guaranteed unless you modify the labels used on the chart's deployments.
+Use the workaround below to upgrade from versions previous to 3.0.0. The following example assumes that the release name is jasperreports:
+
+```console
+$ kubectl patch deployment jasperreports-jasperreports --type=json -p='[{"op": "remove", "path": "/spec/selector/matchLabels/chart"}]'
+$ kubectl delete statefulset jasperreports-mariadb --cascade=false
diff --git a/stable/jasperreports/templates/deployment.yaml b/stable/jasperreports/templates/deployment.yaml
@@ -8,6 +8,10 @@ metadata:
     release: "{{ .Release.Name }}"
     heritage: "{{ .Release.Service }}"
 spec:
+  selector:
+    matchLabels:
+      app: {{ template "jasperreports.fullname" . }}
+      release: "{{ .Release.Name }}"
   template:
     metadata:
       labels: