Stefano Marinelli<p>Another round of “hey, your server is down!” drama from the "we need moar kubernetes!" crowd.</p><p>“I can’t reach your server, it must be down.”</p><p>I connect. Everything’s fine.</p><p>A few emails later, I ask to access the container. The dev says he can’t - doesn’t know how. He’s a nice guy, though, so he gives me the credentials.</p><p>I log in and find the issue: someone pushed a workload to production (cue Kubernetes! Moooaaarrr powaaaarrr! We have the cloud! Who needs sysadmins anymore?!) with DNS set to 192.168.1.1.</p><p>Of course, it fell to me to investigate, because the dev couldn’t even get a shell inside his container. And it's ok, as he's a dev - and just wants to be a dev.</p><p>Once I pointed it out, they rebuilt the container with the correct config and - TADA! - everything worked again.</p><p>Then he went to check other workloads (for other clients, not managed by me) that had been having issues for weeks... Same problem.</p><p>It was DNS.<br>But it wasn't DNS.</p><p><a href="https://mastodon.bsd.cafe/tags/IT" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>IT</span></a> <a href="https://mastodon.bsd.cafe/tags/SysAdmin" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>SysAdmin</span></a> <a href="https://mastodon.bsd.cafe/tags/DNS" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>DNS</span></a> <a href="https://mastodon.bsd.cafe/tags/Cloud" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Cloud</span></a> <a href="https://mastodon.bsd.cafe/tags/DevOps" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>DevOps</span></a></p>