Skip to content

Clock Synchronization

Welkin follows best practices from ntp.se regarding clock synchronization by default. This ensures reliable synchronization with at least two clock sources using NTP servers.

Clock synchronization is important for the following reasons:

  • Several Kubernetes components, in particular etcd, Rook/Ceph, do not work correctly if Nodes' clock drifts by more than 100ms;
  • Several data protection regulations require it.

Be aware of the following:

  • Some regulations require synchronization with at least two clock sources. This could be two different NTP servers which can be traced to two different atomic clocks.
  • Some regulations require synchronization with a specific time source. For example, MSBFS 2020:7 4 kap. 13 § specifically requires synchronization with ntp.se.