<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>CNCF on Flatcar Container Linux</title>
    <link>/tags/cncf/</link>
    <description>Recent content in CNCF on Flatcar Container Linux</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <copyright>Copyright © The Flatcar Project Contributors.

Copyright © Flatcar a Series of LF Projects, LLC.

For website terms of use, trademark policy and other project policies please see &lt;a href=&#34;https://lfprojects.org/policies/&#34;&gt;lfprojects.org/policies&lt;/a&gt;.
</copyright>
    <lastBuildDate>Thu, 27 Feb 2025 00:22:13 +0200</lastBuildDate>
    <atom:link href="/tags/cncf/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Learning from the Flatcar DNS Outage – A Post-Mortem</title>
      <link>/blog/2025/02/learning-from-the-flatcar-dns-outage-a-post-mortem/</link>
      <pubDate>Thu, 27 Feb 2025 00:22:13 +0200</pubDate>
      <guid>/blog/2025/02/learning-from-the-flatcar-dns-outage-a-post-mortem/</guid>
      <description>&lt;p&gt;On February 2nd and 3rd, 2025, Flatcar experienced a significant DNS outage that affected our update and release servers, as well as parts of our CI/CD infrastructure.&#xA;As a result, users were unable to download new Flatcar releases, retrieve Flatcar images for several hours. The root cause was a miscommunication during a domain transfer, which led to DNS mis-configurations.&lt;/p&gt;&#xA;&lt;p&gt;In collaboration with the Linux Foundation (LF) IT team, we have conducted a full post-mortem analysis to understand the issue, improve our processes, and ensure greater reliability for the Flatcar community moving forward.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
