<?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>Openshift on marek@mahut.dev</title><link>https://marek.mahut.dev/tags/openshift/</link><description>Recent content in Openshift on marek@mahut.dev</description><generator>Hugo</generator><language>en</language><lastBuildDate>Thu, 08 Jan 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://marek.mahut.dev/tags/openshift/index.xml" rel="self" type="application/rss+xml"/><item><title>Repurposing My Raspberry Pi 5 (16 GB) for MicroShift</title><link>https://marek.mahut.dev/post/rpi5-microshift/</link><pubDate>Thu, 08 Jan 2026 00:00:00 +0000</pubDate><guid>https://marek.mahut.dev/post/rpi5-microshift/</guid><description>&lt;p&gt;My Raspberry Pi 5 with 16 GB of RAM had been sitting mostly idle for a few months — running the usual homelab suspects, nothing that really pushed it. Then MicroShift caught my eye. A single-binary OpenShift/Kubernetes distro built for edge devices, maintained by Red Hat, targeting exactly the kind of constrained ARM hardware I had on my desk. I decided to give it a proper shot.&lt;/p&gt;
&lt;h2 id="why-microshift"&gt;Why MicroShift&lt;/h2&gt;
&lt;p&gt;I&amp;rsquo;ve been working with OpenShift professionally for a while, and the appeal of having a real OCP-compatible cluster at home — one that speaks the same APIs, uses the same RBAC model, and supports the same operator patterns — is hard to overstate. Alternatives like k3s or microk8s are fine, but they diverge enough that you&amp;rsquo;re always translating. MicroShift is a subset, not a fork. Anything I test locally maps directly to what runs in production.&lt;/p&gt;</description></item></channel></rss>