fix deployment when upgrade (#8027)

Signed-off-by: cpanato <ctadeu@gmail.com>
This commit is contained in:
Carlos Tadeu Panato Junior
2018-09-28 06:07:41 -07:00
committed by k8s-ci-robot
parent 0a5ddac35d
commit b430bbf92c
4 changed files with 10 additions and 2 deletions
+1 -1
View File
@@ -1,7 +1,7 @@
apiVersion: v1
description: Mattermost Team Edition server.
name: mattermost-team-edition
version: 1.1.1
version: 1.1.2
appVersion: 5.3.1
keywords:
- mattermost
+1
View File
@@ -47,6 +47,7 @@ Parameter | Description | Default
--- | --- | ---
`image.repository` | container image repository | `mattermost/mattermost-team-edition`
`image.tag` | container image tag | `5.3.1`
`revisionHistoryLimit` | How many old ReplicaSets for Mattermost Deployment you want to retain | `1`
`config.SiteUrl` | The URL that users will use to access Mattermost. ie `https://mattermost.mycompany.com` | ``
`config.SiteName` | Name of service shown in login screens and UI | `Mattermost`
`config.FilesAccessKey` | The AWS Access Key, if you want store the files on S3 | ``
@@ -8,7 +8,11 @@ metadata:
release: {{ .Release.Name }}
heritage: {{ .Release.Service }}
spec:
replicas: {{ .Values.replicaCount }}
replicas: 1
strategy:
type: Recreate
rollingUpdate: null
revisionHistoryLimit: {{ .Values.revisionHistoryLimit }}
selector:
matchLabels:
app: {{ template "mattermost-team-edition.fullname" . }}
@@ -6,6 +6,9 @@ image:
tag: 5.3.1
imagePullPolicy: IfNotPresent
## How many old ReplicaSets for Mattermost Deployment you want to retain
revisionHistoryLimit: 1
## Enable persistence using Persistent Volume Claims
## ref: http://kubernetes.io/docs/user-guide/persistent-volumes/
## ref: https://docs.gitlab.com/ee/install/requirements.html#storage