4 ms·
TLDR: Ubuntu unattended-upgrades and the systemd-networkd `ManageForeignRoutes=true` [1] default broke all Kubernetes networking globally, across multiple regio
by terom 3y ago
TLDR: Ubuntu unattended-upgrades and the systemd-networkd `ManageForeignRoutes=true` [1] default broke all Kubernetes networking globally, across multiple regions and cloud providers simultaneously, at 06:xx UTC. Recovery was difficult and slow due to the scale, particularly with cloud auto-scaling behavior kinda making things worse when all nodes failed simultaneously.
Please test how `systemctl restart systemd-networkd` affects your custom networking setup. It is quite likely to break.
DataDog also published their own post-mortem: [2]
[1] https://www.freedesktop.org/software/systemd/man/networkd.conf.html#ManageForeignRoutes= https://www.freedesktop.org/software/systemd/man/networkd.co...
[2] https://www.datadoghq.com/blog/2023-03-08-multiregion-infrastructure-connectivity-issue/ https://www.datadoghq.com/blog/2023-03-08-multiregion-infras...
- throwaway67743 3y agoI find it odd they hadn't seen this before, even with a moderate amount of route updates networkd will consume an excessive amount of CPU (even with foreign routes disabled it still processes netlink messages, annoyingly) - this is a pretty rookie thing to miss for a metrics company to be honest