<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Supermicro on Thomas Peters</title><link>https://www.sirmysterion.com/tags/supermicro/</link><description>Recent content in Supermicro on Thomas Peters</description><generator>Hugo</generator><language>en</language><managingEditor>thomas@tnepeters.com (Thomas Peters)</managingEditor><webMaster>thomas@tnepeters.com (Thomas Peters)</webMaster><copyright>&lt;a href="https://creativecommons.org/licenses/by-nc/4.0/" target="_blank" rel="noopener"&gt;CC BY-NC 4.0&lt;/a&gt;</copyright><lastBuildDate>Sat, 25 Jul 2026 23:14:32 -0600</lastBuildDate><atom:link href="https://www.sirmysterion.com/tags/supermicro/index.xml" rel="self" type="application/rss+xml"/><item><title>Bare-Metal Talos on a Recycled Supermicro 4-Node Chassis</title><link>https://www.sirmysterion.com/posts/20260727-baremetal-talos-supermicro/</link><pubDate>Mon, 27 Jul 2026 00:00:00 +0000</pubDate><author>thomas@tnepeters.com (Thomas Peters)</author><guid>https://www.sirmysterion.com/posts/20260727-baremetal-talos-supermicro/</guid><description>&lt;h1 id="the-problem"&gt;The Problem&lt;/h1&gt;
&lt;p&gt;My previous production cluster (talos-02) ran as Proxmox VMs.
It worked, but every VM layer between Kubernetes and the hardware is one more thing to manage, one more network hop to debug, and one more place to lose performance.
When a used Supermicro 2028TP-HC showed up at a reasonable price, the plan wrote itself:
four independent nodes in a 2U chassis, each with 2x Xeon E5-2630 v3 and 64GB of RAM.&lt;/p&gt;</description></item></channel></rss>