Merge pull request #1646 from efazenda/add_update_strategy_deployment

Add update strategy deployment

Author: jertel

CHANGELOG.md

@@ -7,8 +7,10 @@
 - [MicrosoftPowerAutomate] Add support for 'ms_power_automate_webhook_url_from_field' option to dynamically select the webhook URL from the match. - [#1623](https://github.com/jertel/elastalert2/pull/1623) - @aizerin
 - Add Webex Incoming Webhook alerter - [#1635](https://github.com/jertel/elastalert2/pull/1635) - @dennis-trapp
 - Support jinja2 templates in `alertmanager_labels` and `alertmanager_annotations` - [#1642](https://github.com/jertel/elastalert2/pull/1642) - @tgxworld
+- [Helm] Add support of update strategy in the deployment [#1646](https://github.com/jertel/elastalert2/pull/1646) - @efazenda
 - Add Flashduty alerter - [#1649](https://github.com/jertel/elastalert2/pull/1649) - @pijiang3
 
+
 ## Other changes
 - Fix `schema.yaml` to support Kibana 8.17 - [#1631](https://github.com/jertel/elastalert2/pull/1631) - @vpiserchia
 - [Helm] Clarified documentation around rootRulesFolder - @jertel

chart/elastalert2/README.md

@@ -59,6 +59,7 @@ The command removes all the Kubernetes components associated with the chart and
 | `command`                                    | command override for container                                                                                                | `NULL`                                                   |
 | `args`                                       | args override for container                                                                                                   | `NULL`                                                   |
 | `replicaCount`                               | number of replicas to run                                                                                                     | 1                                                        |
+| `updateStrategy.type`                               | update strategy to use                                                                                                     | RollingUpdate                                                        |
 | `minReadySeconds`                            | # number of seconds for which a newly created Pod should be ready without any of its containers crashing, for it to be considered available                                                                                          | 5                                                        |
 | `rulesFolder`                                | Locaton of rules directory. Useful when you have one Docker image and different set of rules per environemnt.                 | /opt/elastalert/rules                                    |
 | `elasticsearch.host`                         | elasticsearch endpoint to use                                                                                                 | elasticsearch                                            |

chart/elastalert2/templates/deployment.yaml

@@ -18,6 +18,9 @@ spec:
     matchLabels:
       {{- include "common.labels.matchLabels" . | nindent 6 }}
   replicas: {{ .Values.replicaCount }}
+  {{- if .Values.updateStrategy }}
+  strategy: {{- toYaml .Values.updateStrategy | nindent 4 }}
+  {{- end }}
   revisionHistoryLimit: {{ .Values.revisionHistoryLimit }}
   minReadySeconds: {{ .Values.minReadySeconds }}
   template:

chart/elastalert2/values.yaml

@@ -16,6 +16,11 @@ appKubernetesIoComponent: elastalert2
 # number of replicas to run
 replicaCount: 1
 
+# update strategy to use (default : RollingUpdate) but can be Recreate
+updateStrategy:
+  type: RollingUpdate
+  rollingUpdate: {}
+
 # number of helm release revisions to retain
 revisionHistoryLimit: 5