[bitnami/consul] Fix chart not being upgradable

Signed-off-by: Javier J. Salmeron Garcia <jsalmeron@bitnami.com>
This commit is contained in:
Javier J. Salmeron Garcia
2018-09-21 13:21:55 +02:00
parent 27e00b2c30
commit d91d4b2f6a
3 changed files with 16 additions and 1 deletions

View File

@@ -2,7 +2,7 @@ name: consul
home: https://www.consul.io/
sources:
- https://github.com/bitnami/consul
version: 1.1.0
version: 2.0.0
appVersion: 1.0.6
description: Highly available and distributed service discovery and key-value store
designed with support for the modern data center to make distributed systems and

View File

@@ -235,3 +235,14 @@ helm install bitnami/consul --set tlsEncryptionSecretName=consul-tls-encryption
## Metrics
The chart can optionally start a metrics exporter endpoint on port `9107` for [prometheus](https://prometheus.io). The data exposed by the endpoint is intended to be consumed by a prometheus chart deployed within the cluster and as such the endpoint is not exposed outside the cluster.
## Upgrading
### To 2.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 2.0.0. The following example assumes that the release name is consul:
```console
$ kubectl delete statefulset consul --cascade=false
```

View File

@@ -8,6 +8,10 @@ metadata:
release: {{ .Release.Name | quote }}
heritage: {{ .Release.Service | quote }}
spec:
selector:
matchLabels:
app: {{ template "consul.name" . }}
release: "{{ .Release.Name }}"
serviceName: "{{ template "consul.fullname" . }}"
replicas: {{ default 3 .Values.replicas }}
updateStrategy: