matrix-synapse: Add deployment strategy configuration for pods
This commit is contained in:
parent
d06d28972d
commit
f246c4fe2d
3 changed files with 23 additions and 0 deletions
|
@ -16,6 +16,8 @@ metadata:
|
||||||
app.kubernetes.io/component: synapse
|
app.kubernetes.io/component: synapse
|
||||||
spec:
|
spec:
|
||||||
replicas: 1
|
replicas: 1
|
||||||
|
strategy:
|
||||||
|
{{- toYaml .Values.synapse.strategy | nindent 4 }}
|
||||||
selector:
|
selector:
|
||||||
matchLabels:
|
matchLabels:
|
||||||
{{- include "matrix-synapse.selectorLabels" . | nindent 6 }}
|
{{- include "matrix-synapse.selectorLabels" . | nindent 6 }}
|
||||||
|
|
|
@ -13,6 +13,10 @@ metadata:
|
||||||
app.kubernetes.io/component: {{ $name }}
|
app.kubernetes.io/component: {{ $name }}
|
||||||
spec:
|
spec:
|
||||||
replicas: {{ $config.replicaCount | default $default.replicaCount }}
|
replicas: {{ $config.replicaCount | default $default.replicaCount }}
|
||||||
|
{{- with ($config.strategy | default $default.strategy) }}
|
||||||
|
strategy:
|
||||||
|
{{- toYaml . | nindent 4 }}
|
||||||
|
{{- end }}
|
||||||
selector:
|
selector:
|
||||||
matchLabels:
|
matchLabels:
|
||||||
{{- include "matrix-synapse.selectorLabels" $ | nindent 6 }}
|
{{- include "matrix-synapse.selectorLabels" $ | nindent 6 }}
|
||||||
|
|
|
@ -145,6 +145,15 @@ extraSecrets: {}
|
||||||
## Configuration to apply to the main Synapse pod.
|
## Configuration to apply to the main Synapse pod.
|
||||||
##
|
##
|
||||||
synapse:
|
synapse:
|
||||||
|
## Only really applicable when the deployment has an RWO PV attached (e.g. when media repository
|
||||||
|
## is enabled for the main Synapse pod)
|
||||||
|
## Since replicas = 1, an update can get "stuck", as the previous pod remains attached to the
|
||||||
|
## PV, and the "incoming" pod can never start. Changing the strategy to "Recreate" will
|
||||||
|
## terminate the single previous pod, so that the new, incoming pod can attach to the PV
|
||||||
|
##
|
||||||
|
strategy:
|
||||||
|
type: RollingUpdate
|
||||||
|
|
||||||
## Annotations to apply to the main Synapse pod.
|
## Annotations to apply to the main Synapse pod.
|
||||||
##
|
##
|
||||||
annotations: {}
|
annotations: {}
|
||||||
|
@ -260,6 +269,14 @@ workers:
|
||||||
##
|
##
|
||||||
replicaCount: 1
|
replicaCount: 1
|
||||||
|
|
||||||
|
## Update strategy - only really applicable for deployments with RWO PVs attached (e.g. media repository)
|
||||||
|
## If replicas = 1, an update can get "stuck", as the previous pod remains attached to the
|
||||||
|
## PV, and the "incoming" pod can never start. Changing the strategy to "Recreate" will
|
||||||
|
## terminate the single previous pod, so that the new, incoming pod can attach to the PV
|
||||||
|
##
|
||||||
|
strategy:
|
||||||
|
type: RollingUpdate
|
||||||
|
|
||||||
## A specific name for this worker, can't be set globally.
|
## A specific name for this worker, can't be set globally.
|
||||||
## Note that this can only be set when replicaCount is 1
|
## Note that this can only be set when replicaCount is 1
|
||||||
#name:
|
#name:
|
||||||
|
|
Loading…
Reference in a new issue