Skip to content

Commit

Permalink
Add ability to set the deployment strategy
Browse files Browse the repository at this point in the history
The default strategy is `RollingUpdate` which does not work well with
volume claims: they cannot be attached to the new contained, blocking
it from starting up. This commit allows the user to override this
strategy if needed.
  • Loading branch information
Michel Wilson committed Sep 5, 2023
1 parent 5307e1e commit 101d77f
Show file tree
Hide file tree
Showing 2 changed files with 3 additions and 0 deletions.
2 changes: 2 additions & 0 deletions chart/bitwarden-k8s/templates/deployment.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -15,6 +15,8 @@ metadata:
app.kubernetes.io/managed-by: {{ .Release.Service }}
spec:
replicas: {{ .Values.replicaCount }}
strategy:
type: {{ .Values.deployStrategy }}
selector:
matchLabels:
app.kubernetes.io/name: {{ include "bitwarden-k8s.name" . }}
Expand Down
1 change: 1 addition & 0 deletions chart/bitwarden-k8s/values.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -3,6 +3,7 @@
# Declare variables to be passed into your templates.

replicaCount: 1
deployStrategy: RollingUpdate

image:
repository: bitwardenrs/server
Expand Down

0 comments on commit 101d77f

Please sign in to comment.