<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Bootc on SREKubeCraft | Nick Nikolakakis</title><link>https://srekubecraft.io/tags/bootc/</link><description>Recent content in Bootc on SREKubeCraft | Nick Nikolakakis</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Sat, 26 Sep 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://srekubecraft.io/tags/bootc/index.xml" rel="self" type="application/rss+xml"/><item><title>Immutable Kubernetes Nodes as OCI Images - A Close Look at bootc</title><link>https://srekubecraft.io/posts/immutable-kubernetes-nodes-as-oci-images-bootc/</link><pubDate>Sat, 26 Sep 2026 00:00:00 +0000</pubDate><guid>https://srekubecraft.io/posts/immutable-kubernetes-nodes-as-oci-images-bootc/</guid><description>&lt;p&gt;Every self-managed cluster I have inherited had the same artefact sitting in a corner: a Packer template nobody wanted to touch. It produced the AMI, the AMI produced the node pool, and somewhere between those two steps a &lt;code&gt;dnf update&lt;/code&gt; ran against whatever the mirror happened to be serving that morning. Two nodes built three months apart were not the same machine, and the only way to find out how they differed was to SSH into both and start diffing.&lt;/p&gt;</description></item></channel></rss>