Skip to main content

Azure Kubernetes Service - Time sync issue between nodes

We encountered a strange issue this week inside our AKS cluster. We discovered that the time was not synced between the different pods and nodes.

We noticed this because we couldn’t use our  OAuth security tokens as the IssuedAt timing was off.

To validate this issue we ssh’d into the nodes and ran the following command:

$: sudo timedatectl status

This resulted in the following output

Local time: Wed 2021-6-2 13:48:44 UTC
Universal time: Wed 2021-6-2 13:48:44 UTC
RTC time: Wed 2021-6-2 13:48:44
Time zone: Etc/UTC (UTC, +0000)
Network time on: yes
NTP synchronized: no
RTC in local TZ: no

The NTP service was disabled and no NTP service was configured. To fix it we opened the timesyncd.conf:

$: sudo cat /etc/systemd/timesyncd.conf

and changed the NTP value

[Time]
NTP=ntp.ubuntu.com

After that we restarted the timesync service:

$: sudo timedatectl set-ntp true
$: sudo systemctl restart systemd-timesyncd.service

Of course this is only good as a temporary workaround. I would expect that this is enabled by default.

Popular posts from this blog

Azure DevOps/ GitHub emoji

I’m really bad at remembering emoji’s. So here is cheat sheet with all emoji’s that can be used in tools that support the github emoji markdown markup: All credits go to rcaviers who created this list.

.NET 8–Keyed/Named Services

A feature that a lot of IoC container libraries support but that was missing in the default DI container provided by Microsoft is the support for Keyed or Named Services. This feature allows you to register the same type multiple times using different names, allowing you to resolve a specific instance based on the circumstances. Although there is some controversy if supporting this feature is a good idea or not, it certainly can be handy. To support this feature a new interface IKeyedServiceProvider got introduced in .NET 8 providing 2 new methods on our ServiceProvider instance: object? GetKeyedService(Type serviceType, object? serviceKey); object GetRequiredKeyedService(Type serviceType, object? serviceKey); To use it, we need to register our service using one of the new extension methods: Resolving the service can be done either through the FromKeyedServices attribute: or by injecting the IKeyedServiceProvider interface and calling the GetRequiredKeyedServic...

Kubernetes–Limit your environmental impact

Reducing the carbon footprint and CO2 emission of our (cloud) workloads, is a responsibility of all of us. If you are running a Kubernetes cluster, have a look at Kube-Green . kube-green is a simple Kubernetes operator that automatically shuts down (some of) your pods when you don't need them. A single pod produces about 11 Kg CO2eq per year( here the calculation). Reason enough to give it a try! Installing kube-green in your cluster The easiest way to install the operator in your cluster is through kubectl. We first need to install a cert-manager: kubectl apply -f https://github.com/cert-manager/cert-manager/releases/download/v1.14.5/cert-manager.yaml Remark: Wait a minute before you continue as it can take some time before the cert-manager is up & running inside your cluster. Now we can install the kube-green operator: kubectl apply -f https://github.com/kube-green/kube-green/releases/latest/download/kube-green.yaml Now in the namespace where we want t...