<rss version="2.0">
  <channel>
    <title>Blog</title>
    <link>https://clearthesky.eu/</link>
    <description><![CDATA[<p>Self-hosted infrastructure, open-source tools, and digital sovereignty — from the team at Clear The Sky.</p>]]></description>
    <item>
      <title>Buying the Hardware</title>
      <link>https://clearthesky.eu/blog/buying-the-hardware</link>
      <description><![CDATA[<p>When we decided to build our own self-hosted infrastructure, the first question was: what hardware do we need?</p>
<h2>The Requirements</h2>
<p>We needed a platform that could run a full Kubernetes cluster with multiple services. The key requirements were:</p>
<ul>
<li><strong>Redundancy</strong>: At least two physical hosts</li>
<li><strong>Performance</strong>: Enough CPU and RAM for 30+ containers</li>
<li><strong>Storage</strong>: Fast local disks for databases plus a NAS for bulk data</li>
<li><strong>Low power</strong>: Energy efficiency for 24/7 operation</li>
<li><strong>Quiet</strong>: Home office, not a datacenter</li>
</ul>
<h2>What We Chose</h2>
<p>We settled on two compact mini-PCs with AMD Ryzen processors. Each host runs Proxmox as the hypervisor, with K3s Kubernetes VMs on top. A Synology NAS handles shared storage via NFS.</p>
<h2>The Setup</h2>
<p>Each server has:</p>
<ul>
<li>AMD Ryzen processor with integrated GPU</li>
<li>32 GB DDR5 RAM</li>
<li>500 GB NVMe SSD for the OS</li>
<li>500 GB dedicated SSD for Longhorn block storage</li>
</ul>
<p>The Synology NAS provides 4 TB of shared storage for media, backups, and NFS volumes.</p>
<h2>Next Up</h2>
<p>In future posts, we will cover the software stack: Proxmox, K3s, ArgoCD, and all the self-hosted applications.</p>
]]></description>
      <pubDate>Fri, 06 Mar 2026 12:00:00 GMT</pubDate>
      <guid isPermaLink="true">https://clearthesky.eu/blog/buying-the-hardware</guid>
    </item>
  </channel>
</rss>