Re: Chrony launched with -x in Kubernetes

Hi,

Thank your for your qui quick response !
So, if I understood you correctly, if I set the time sources of the chrony
in the OS to the same internet sources as the ones used in the chrony pod
it will break the loop ?

Best regards,

Nate

Le lun. 21 oct. 2024, 12:23, Miroslav Lichvar <[email protected]> a
écrit :

> On Mon, Oct 21, 2024 at 11:42:04AM +0200, Nathan MALO wrote:
> > Am I in a situation where "the snake bites its own tail" ?
> > That somehow there is a loop between the chrony pod and the chrony in the
> > OS running on the node that runs the chrony pod ?
>
> Yes, there is a feedback loop between the two chronyd instances. The
> one running with -x does not adjust the system clock, but it still
> uses it as a reference and assumes it is reasonably stable.
>
> You need to break the loop. The instance adjusting the clock needs to
> synchronize to servers that don't have this clock in their
> synchronization path.
>
> Note that chronyd doesn't need to be started with root privileges to
> be able to control the clock. See the -U option in the man page and
> the example chronyd-restricted.service in the source code.
>
> --
> Miroslav Lichvar
>
>
> --
> To unsubscribe email chrony-users-request-kWFZVVI9zxvPqho9SqqRMmD2FQJk+8+b@public.gmane.org
> with "unsubscribe" in the subject.
> For help email chrony-users-request-kWFZVVI9zxvPqho9SqqRMmD2FQJk+8+b@public.gmane.org
> with "help" in the subject.
> Trouble?  Email [email protected]
>
>