Skip to content

Configure Timezone

Helm Chart Value

By default, time zone of all containers in the Helm-based DX deployment is in UTC.

You can configure this by updating the incubator.containerTimezone field in the custom values file.

Before applying the changes make sure you understand the implication of updating the timezone in all the applications.

Important

If you are using DAM Staging and/or WCM Syndication all deployments must have the same timezone, to prevent issues during synchronization.

See supported input types for examples of valid timezone formats.

For example to use GMT/BST you need to set the incubator.containerTimezone to Europe/London 

incubator:
  containerTimezone: "Europe/London"

And then apply the changes using the following command:

helm upgrade -n <namespace> -f <custom-values.yaml> <prefix> <chart>

If you wish to go back to the UTC, you can just pass an empty string to the incubator.containerTimezone field.

Note

If you passed an invalid time zone, the time zone would default back to UTC.

Effects

Changing the incubator.containerTimezone value in custom values file changes the time zone for all containers.

This also means that the application running inside the containers is also affected by this change.

Effects of changing the time zone depends on the application, but some examples are:

  • TZ environment variable is set for all containers.
  • Timestamps of files inside the container reflect the set timezone.
  • CRON Jobs of Prereqs Checker follow the new time zone. For more information, see the Prereqs Checker Documentation.
  • Timestamps of the logs are currently partially affected depending on each application's logging framework. Some of the logs adapt the timezone of the container, while others always log UTC timestamps.

Uniform log timestamps

Currently, depending on the logging solution used inside each container, the logs do not reflect the timezone uniformly. To get uniform log timestamps with kubectl, the --timestamps flag can be passed to kubectl logs. This prepends all log outputs with a UTC timestamp.

Supported Input Types

Some Examples:

  • Europe/London
  • Australia/Melbourne
  • America/Phoenix

You can use any timezone that are in the Timezone DB database. For the comprehensive list please see this list of time zones you can use values from the TZ database name column.