GDB-11193: Time zone configurations for the backup cron job

Added a new configuration that allows to override the default timezone
which usually is the local timezone.

CHANGELOG.md

@@ -19,6 +19,7 @@
   - Added `cluster.tls.certificateRevocationList` to configure a certificate revocation list
 - Updated jobs and scripts to use `https` or `http` depending on whether the Tomcat connector security is configured
 - Added `indices` configuration enabling a job for initial preloading of indices and other SPARQL updates
+- Added `backup.timezone` configuration for overriding the default timezone with a specific one
 
 ## Version 11.3.3
 

templates/jobs/cronjob-backup.yaml

@@ -12,6 +12,9 @@ metadata:
   {{- end }}
 spec:
   schedule: {{ .Values.backup.schedule | quote }}
+  {{- if and .Values.backup.timezone (semverCompare ">=1.27-0" .Capabilities.KubeVersion.Version) }}
+  timeZone: {{ .Values.backup.timezone }}
+  {{- end }}
   successfulJobsHistoryLimit: {{ .Values.backup.successfulJobsHistoryLimit }}
   failedJobsHistoryLimit: {{ .Values.backup.failedJobsHistoryLimit }}
   concurrencyPolicy: Forbid

values.yaml

@@ -756,6 +756,12 @@ backup:
   # Ref: https://kubernetes.io/docs/concepts/workloads/controllers/cron-jobs/#schedule-syntax
   schedule: "@midnight"
 
+  # Specifies the time zone for the cron job. If not specified, Kubernetes will use the local time zone by default.
+  # This requires Kubernetes v1.27 or greater.
+  #
+  # Ref: https://kubernetes.io/docs/concepts/workloads/controllers/cron-jobs/#time-zones
+  timezone: ""
+
   # Backup options that will be injected as JSON in the default backup options Secret. \
   # These configurations define the backup behaviour such as including or excluding repositories or system data.
   #