<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>mtu on bascht.com</title><link>https://bascht.com/tags/mtu/</link><description>Recent content in mtu on bascht.com</description><generator>Hugo -- gohugo.io</generator><language>de-de</language><lastBuildDate>Thu, 08 Apr 2021 00:00:00 +0000</lastBuildDate><atom:link href="https://bascht.com/tags/mtu/index.xml" rel="self" type="application/rss+xml"/><item><title>Kubernetes Docker dind MTU issues on Hetzner (Cloud)</title><link>https://bascht.com/tech/2021/04/08/kubernetes-docker-dind-mtu-issues-on-hetzner-cloud/</link><pubDate>Thu, 08 Apr 2021 00:00:00 +0000</pubDate><guid>https://bascht.com/tech/2021/04/08/kubernetes-docker-dind-mtu-issues-on-hetzner-cloud/</guid><description>(angrily-typed-after-a-wasted-night-of-debugging)
Recently we used Hetzners new vSwitch subnets to start adding dedicated servers to one of our Kubernetes Clusters. Especially for CI workloads where we don&amp;#39;t need persistent storage, this is really cost-effective, as we could basically replace 4 other worker nodes with a single cheaper node.
Upon spawning the first GitLab runner pods on the new node things went south: We saw random build failures bubbling up in jobs that didn&amp;#39;t fail for ages:</description></item></channel></rss>