[stable/owncloud] Fix chart not being upgradable (#7844)

Signed-off-by: Javier J. Salmeron Garcia <jsalmeron@bitnami.com>
This commit is contained in:
Javier J. Salmerón-García
2018-09-20 07:35:20 -07:00
committed by k8s-ci-robot
parent 8f18f4f756
commit fd1f962f4f
3 changed files with 17 additions and 1 deletions
+1 -1
View File
@@ -1,5 +1,5 @@
name: owncloud
version: 2.0.6
version: 3.0.0
appVersion: 10.0.10
description: A file sharing server that puts the control and security of your own data back into your hands.
keywords:
+12
View File
@@ -126,3 +126,15 @@ The [Bitnami ownCloud](https://github.com/bitnami/bitnami-docker-owncloud) image
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 owncloud:
```console
$ kubectl patch deployment owncloud-owncloud --type=json -p='[{"op": "remove", "path": "/spec/selector/matchLabels/chart"}]'
$ kubectl delete statefulset owncloud-mariadb --cascade=false
```
@@ -9,6 +9,10 @@ metadata:
release: "{{ .Release.Name }}"
heritage: "{{ .Release.Service }}"
spec:
selector:
matchLabels:
app: {{ template "owncloud.fullname" . }}
release: "{{ .Release.Name }}"
replicas: 1
template:
metadata: