<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Proxmox on Gerard Samuel</title><link>https://gerardsamuel.me/tags/proxmox/</link><description>Recent content in Proxmox on Gerard Samuel</description><generator>Hugo -- gohugo.io</generator><language>en</language><lastBuildDate>Fri, 02 Aug 2024 17:31:04 -0400</lastBuildDate><atom:link href="https://gerardsamuel.me/tags/proxmox/index.xml" rel="self" type="application/rss+xml"/><item><title>How to Setup a Proxmox Cluster</title><link>https://gerardsamuel.me/posts/how-to-setup-a-proxmox-cluster/</link><pubDate>Fri, 02 Aug 2024 17:31:04 -0400</pubDate><guid>https://gerardsamuel.me/posts/how-to-setup-a-proxmox-cluster/</guid><description>&lt;p&gt;I needed a means of spinning up virtual machines to try out solutions such as Kubernetes or GitLab runners, etc, on a long-term basis. I did not want to incur the cost of running operating systems on Cloud Infrastructure. ESXi was definitely not happening, as Broadcom had muddied the waters at the time. At first, I tried &lt;a href="https://www.proxmox.com/en/" target="_blank" rel="noreferrer"&gt;Proxmox&lt;/a&gt;, and then I tried Suse &lt;a href="https://harvesterhci.io/" target="_blank" rel="noreferrer"&gt;Harvester&lt;/a&gt;. I contemplated &lt;a href="https://xcp-ng.org/" target="_blank" rel="noreferrer"&gt;XCP-ng&lt;/a&gt;. After weighing what I needed, I settled back to Proxmox VE.&lt;/p&gt;</description><media:content xmlns:media="http://search.yahoo.com/mrss/" url="https://gerardsamuel.me/posts/how-to-setup-a-proxmox-cluster/featured.webp"/></item></channel></rss>