https://polar-node.work/tags/proxmox/Recent content in Proxmox on polar-node // runbooksHugoen-usFri, 19 Jun 2026 00:00:00 +0000https://polar-node.work/projects/zabbix-ha-cluster/Fri, 19 Jun 2026 00:00:00 +0000https://polar-node.work/projects/zabbix-ha-cluster/<p><strong>Status: in progress.</strong></p> <p>A fully redundant Zabbix monitoring stack, deployed entirely through code rather than manual configuration:</p> <ul> <li><strong>Multi-node Zabbix server cluster</strong> — native Zabbix HA nodes for server-level failover</li> <li><strong>Distributed Zabbix proxies</strong> — spread across network segments or regions for resilient, scalable data collection</li> <li><strong>Clustered database backend</strong> — the catalog/history database itself deployed as a cluster, not a single point of failure</li> <li><strong>Infrastructure as Code</strong> — the entire stack reproducible from a single set of Terraform/Ansible definitions</li> </ul> <p>The goal is portability: the same IaC definitions should stand up the cluster identically whether the target is <strong>on-premise Proxmox VE</strong>, or a public cloud — <strong>AWS</strong>, <strong>Azure</strong>, or <strong>GCP</strong>. Same architecture, same automation, different provider underneath.</p>https://polar-node.work/posts/proxmox-cloud-init-template-creator/Mon, 15 Jun 2026 00:00:00 +0000https://polar-node.work/posts/proxmox-cloud-init-template-creator/<h2 id="the-problem">The problem</h2> <p>There&rsquo;s something innate in some people — the drive to fix whatever is annoying. Annoying to some, but apparently default behavior for others.</p> <p>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.</p>