mirror of
https://github.com/matrix-org/dendrite.git
synced 2025-12-06 14:33:10 -06:00
fix(helm): change strategy to Recreate
Current dendrite needs an PVC and replica of 1 is forced, so best way of update and change of configuration is to stop and start (instatt of start multiple dendrite pod with deadlock of binding pvc) see: #3258 Signed-off-by: WrenIX <dev.github@wrenix.eu>
This commit is contained in:
parent
be0c27e688
commit
1d4e304297
|
|
@ -1,6 +1,6 @@
|
||||||
apiVersion: v2
|
apiVersion: v2
|
||||||
name: dendrite
|
name: dendrite
|
||||||
version: "0.13.7"
|
version: "0.13.8"
|
||||||
appVersion: "0.13.6"
|
appVersion: "0.13.6"
|
||||||
description: Dendrite Matrix Homeserver
|
description: Dendrite Matrix Homeserver
|
||||||
type: application
|
type: application
|
||||||
|
|
|
||||||
|
|
@ -92,7 +92,7 @@ extraVolumeMounts: []
|
||||||
strategy:
|
strategy:
|
||||||
# -- Strategy to use for rolling updates (e.g. Recreate, RollingUpdate)
|
# -- Strategy to use for rolling updates (e.g. Recreate, RollingUpdate)
|
||||||
# If you are using ReadWriteOnce volumes, you should probably use Recreate
|
# If you are using ReadWriteOnce volumes, you should probably use Recreate
|
||||||
type: RollingUpdate
|
type: Recreate
|
||||||
rollingUpdate:
|
rollingUpdate:
|
||||||
# -- Maximum number of pods that can be unavailable during the update process
|
# -- Maximum number of pods that can be unavailable during the update process
|
||||||
maxUnavailable: 25%
|
maxUnavailable: 25%
|
||||||
|
|
|
||||||
Loading…
Reference in a new issue