Skip to content

Commit d13448d

Browse files
authored
Merge pull request #14 from funkypenguin/default-to-strategy-recreate
Default to a strategy of recreate
2 parents d198aec + eaeb832 commit d13448d

5 files changed

Lines changed: 8 additions & 33 deletions

File tree

.circleci/config.yml

Lines changed: 0 additions & 13 deletions
This file was deleted.

.circleci/prep-kubeval.sh

Lines changed: 0 additions & 3 deletions
This file was deleted.

.circleci/prep-unit-tests.sh

Lines changed: 0 additions & 9 deletions
This file was deleted.

charts/docker-mailserver/Chart.yaml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@ apiVersion: v1
22
appVersion: "6.3.0"
33
description: A fullstack but simple mailserver (smtp, imap, antispam, antivirus, ssl...) using Docker.
44
name: docker-mailserver
5-
version: 0.2.4-pre1
5+
version: 0.2.4-pre2
66
sources:
77
- https://github.com/funkypenguin/helm-docker-mailserver
88
maintainers:

charts/docker-mailserver/values.yaml

Lines changed: 7 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -109,13 +109,13 @@ pod:
109109

110110
## Update strategy - only really applicable for deployments with RWO PVs attached
111111
## If replicas = 1, an update can get "stuck", as the previous pod remains attached to the
112-
## PV, and the "incoming" pod can never start. Changing the strategy to "Recreate" will
112+
## PV, and the "incoming" pod can never start. Setting the strategy to "Recreate" (our default) will
113113
## terminate the single previous pod, so that the new, incoming pod can attach to the PV
114-
strategy: {}
114+
strategy:
115115
# rollingUpdate:
116116
# maxSurge: 1
117117
# maxUnavailable: 1
118-
# type: "RollingUpdate"
118+
type: "Recreate"
119119

120120
## The following variables affect the behaviour of docker-mailserver
121121
## See https://github.com/tomav/docker-mailserver#environment-variables for details
@@ -330,13 +330,13 @@ rainloop:
330330

331331
## Update strategy - only really applicable for deployments with RWO PVs attached
332332
## If replicas = 1, an update can get "stuck", as the previous pod remains attached to the
333-
## PV, and the "incoming" pod can never start. Changing the strategy to "Recreate" will
334-
## terminate the single previous pod, so that the new, incoming pod can attach to the PV
335-
strategy: {}
333+
## PV, and the "incoming" pod can never start. Setting the strategy to "Recreate" (our default) will
334+
## terminate the single previous pod, so that the new, incoming pod can attach to the PV.
335+
strategy:
336336
# rollingUpdate:
337337
# maxSurge: 1
338338
# maxUnavailable: 1
339-
# type: "RollingUpdate"
339+
type: "Recreate"
340340

341341
persistence:
342342
size: "1Gi"

0 commit comments

Comments
 (0)