<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Kubernetes on Michael Johnson</title>
    <link>https://ahze.net/tags/kubernetes/</link>
    <description>Recent content in Kubernetes on Michael Johnson</description>
    <image>
      <title>Michael Johnson</title>
      <url>https://ahze.net/images/profile.jpg</url>
      <link>https://ahze.net/images/profile.jpg</link>
    </image>
    <generator>Hugo -- 0.169.0</generator>
    <language>en-us</language>
    <lastBuildDate>Fri, 06 Nov 2026 15:00:00 -0500</lastBuildDate>
    <atom:link href="https://ahze.net/tags/kubernetes/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Firing the Babysitter: Why Daemonless Moved On From s6</title>
      <link>https://ahze.net/posts/moving-on-from-s6/</link>
      <pubDate>Fri, 06 Nov 2026 15:00:00 -0500</pubDate>
      <guid>https://ahze.net/posts/moving-on-from-s6/</guid>
      <description>&lt;p&gt;In April I wrote &lt;a href=&#34;https://ahze.net/posts/daemonless-s6/&#34;&gt;a whole post defending s6&lt;/a&gt; as the init system for daemonless images. I called it the most efficient, C-based babysitter in the business, and ended with a challenge:&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;s6 is the right init system for FreeBSD containers.&lt;/p&gt;
&lt;/blockquote&gt;
&lt;blockquote&gt;
&lt;p&gt;If you disagree — different init system, cleaner pattern, something I missed — make your case on GitHub Discussions. I&amp;rsquo;m genuinely open to being convinced.&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;Seven months later, one app image in the fleet still runs on s6. Kubernetes made the case, and a test I had already run in that post made it worse.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
