Merge pull request #25 from abh/strategy

Support specifying deployment strategy
2020-06-05 11:10:47 -04:00
parent 449cdbc1c0 194cda4c52
commit deb8d4186c
2 changed files with 16 additions and 1 deletions
--- a/templates/deployment.yaml
+++ b/templates/deployment.yaml
@@ -1,4 +1,3 @@
- 
 apiVersion: apps/v1 
 kind: Deployment 
 metadata: 
@@ -13,6 +12,10 @@ spec:
 selector: 
 matchLabels: 
 app: {{ template "fullname" . }} 
+{{- with .Values.deploymentStrategy }} 
+ strategy: 
+{{ toYaml . | trim | indent 4 }} 
+{{- end }} 
 template:  
 metadata: 
 labels: 
--- a/values.yaml
+++ b/values.yaml
@@ -114,6 +114,18 @@ resources:
 memory: 64Mi 
 cpu: 50m 
 
+## Update strategy - for deployments with RWO PVs attached and with a 
+## single replicas = 1, an update can get stuck, as the previous pod 
+## remains attached to the PVC. Changing the strategy to "Recreate" 
+## will terminate the single previous pod, so that the new, incoming 
+## pod can attach to the PV 
+# deploymentStrategy: 
+# rollingUpdate: 
+# type: "Recreate" 
+# type: "RollingUpdate" 
+# maxSurge: 1 
+# maxUnavailable: 1 
+ 
 ## Enable persistence using Persistent Volume Claims 
 ## ref: http://kubernetes.io/docs/user-guide/persistent-volumes/ 
 ## ref: