The nspOS, which is the common resource base of a CLM system, is deployed in a CLM cluster of one VM in the Kubernetes container environment. A disaster-recovery, or DR, deployment, consists of matching CLM clusters in geographically separate data centers. A DR deployment is also called a geo-redundant deployment.

CAUTION Service Degradation

Some entities, for example, members of an etcd cluster, fail to trust data integrity in the presence of a time difference. Failing to closely synchronize the system clocks among components complicates troubleshooting and may cause a service outage.

Ensure that you use only the time service described in this section to synchronize the CLM components.

The system clocks of the CLM components must always be closely synchronized. The RHEL chronyd service is the mandatory time-synchronization mechanism that you must engage on each CLM component during deployment.

Note: Only one time-synchronization mechanism can be active in a CLM system. Before you enable chronyd on a CLM component, you must ensure that no other time-synchronization mechanism, for example, the VMware Tools synchronization utility, is enabled.