ECS unified time zone

You can synchronize the Embedded Container Service (ECS) cluster time zone with the Cloudera Manager Base time zone.

In CDP Private Cloud Data Services versions earlier than 1.5.2, containers running on an ECS Kubernetes cluster did not inherit the time zone settings from the Cloudera Manager Base host. In most cases, Kubernetes containers use Coordinated Universal Time (UTC) by default.

In Private Cloud Data Services 1.5.2 and higher versions, you can unify the time zone in the ECS cluster with the Cloudera Manager Base time zone. All workload pods in the ECS cluster run under the Cloudera Manager time zone, and workload logs on the ECS cluster are correlated with the Cloudera Manager Base logs. Timestamp-related SQL queries are also correlated.

• Unified time zone is enabled by default for new CDP Private Cloud Data Services 1.5.2+ installs.
• When upgrading from earlier versions of CDP Private Cloud Data Services to 1.5.2+, unified time zone is disabled by default to avoid affecting timestamp-sensitive logic.

You can enable or disable unified time zone using the following script in the ECS parcel:

bash /opt/cloudera/parcels/ECS/k8tz-webhook/configure-k8tz-webhook.sh -h

This script modifies the k8tz webhook settings.

Syntax:

configure-k8tz-webhook.sh [-i|-h]

Options:

• i – This option enables the unified time zone feature

• No options – To disable the unified time zone feature, run the configure-k8tz-webhook.sh script without any options.

• Use the -h flag to print Help information

To complete the process of enabling the unified time zone feature:

• Restart the workload pods where you want the Cloudera Manager Server timezone to be applied.

-OR-

• Initiate an ECS cluster rolling restart. This will inject the time zone information into all workload pods.

When the unified time zone feature is disabled, all running pods are not affected. To apply the new disabled setting so they run with the default UTC time zone, a pod restart or a rolling restart is required.