Open asbassan opened 3 years ago
1) Are they using private cluster? because if they are using public cluster - they get ntp from microsoft. 2) On the new host where we had this issue, we need to look at the logs to see why we could not get to ntp or chrony - reopen the old ticket.
we could have been more crisper on what changes are required to pick up the chrony service.
initially happened in april. Aks nodes were losing their time - 2104230010007126. How ntp was set up on aks. There was a new image rolled out having chrony - we got the same issue again - ntp was not running - chrony was not running. that is not a scalable solution - whethere or not we expect those issue. it appeared that chrony was released immidiately but it is not a consistent experience.