You've already forked prometheus-fail2ban-exporter-charts
feat: automatically roll deployments
The following patch extends the chart to automatically roll the deployment, when one of the configurations, stored in a config map or secret, has been changed. The implementation add annotations which triggers `helm update` or ArgoCD to roll the deployment. Further information can be found on the official helm website: https://helm.sh/docs/howto/charts_tips_and_tricks/#automatically-roll-deployments
This commit is contained in:
@ -4,6 +4,21 @@
|
||||
|
||||
{{- define "prometheus-fail2ban-exporter.pod.annotations" -}}
|
||||
{{ include "prometheus-fail2ban-exporter.annotations" . }}
|
||||
|
||||
# The following annotations are required to trigger a rolling update. Further information can be found in the official
|
||||
# documentation of helm:
|
||||
#
|
||||
# https://helm.sh/docs/howto/charts_tips_and_tricks/#automatically-roll-deployments
|
||||
#
|
||||
|
||||
{{/* web config */}}
|
||||
{{- if and .Values.config.webConfig.existingSecret.enabled .Values.config.webConfig.existingSecret.secretName }}
|
||||
{{- $secret := default (dict "data" (dict)) (lookup "v1" "Secret" .Release.Namespace .Values.config.webConfig.existingSecret.secretName ) }}
|
||||
checksum/secret-web-config: {{ print $secret.spec | sha256sum }}
|
||||
{{- else }}
|
||||
checksum/secret-web-config: {{ include (print $.Template.BasePath "/prometheus-fail2ban-exporter/secretWebConfig.yaml") . | sha256sum }}
|
||||
{{- end }}
|
||||
|
||||
{{- end }}
|
||||
|
||||
{{/* labels */}}
|
||||
|
@ -17,6 +17,8 @@ spec:
|
||||
{{- include "prometheus-fail2ban-exporter.pod.selectorLabels" . | nindent 6 }}
|
||||
template:
|
||||
metadata:
|
||||
annotations:
|
||||
{{- include "prometheus-fail2ban-exporter.pod.annotations" . | nindent 8 }}
|
||||
labels:
|
||||
{{- include "prometheus-fail2ban-exporter.pod.labels" . | nindent 8 }}
|
||||
spec:
|
||||
|
Reference in New Issue
Block a user