<?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 polar-node // runbooks</title><link>https://polar-node.work/categories/proxmox/</link><description>Recent content in Proxmox on polar-node // runbooks</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Mon, 15 Jun 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://polar-node.work/categories/proxmox/index.xml" rel="self" type="application/rss+xml"/><item><title>Automating Proxmox VM Template Creation with Cloud-Init</title><link>https://polar-node.work/posts/proxmox-cloud-init-template-creator/</link><pubDate>Mon, 15 Jun 2026 00:00:00 +0000</pubDate><guid>https://polar-node.work/posts/proxmox-cloud-init-template-creator/</guid><description>&lt;h2 id="the-problem"&gt;The problem&lt;/h2&gt;
&lt;p&gt;There&amp;rsquo;s something innate in some people — the drive to fix whatever is annoying. Annoying to some, but apparently default behavior for others.&lt;/p&gt;
&lt;p&gt;Since I started my journey with Proxmox, I was amazed by its capabilities, and every release improved on that foundation. But there was trouble in this newfound paradise: one of the most repetitive tasks was creating a VM almost identical to the previous one. Same base OS, same baseline packages, same manual clicking through the same wizard.&lt;/p&gt;</description></item></channel></rss>