<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Terraform on polar-node // runbooks</title><link>https://polar-node.work/tags/terraform/</link><description>Recent content in Terraform on polar-node // runbooks</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Fri, 19 Jun 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://polar-node.work/tags/terraform/index.xml" rel="self" type="application/rss+xml"/><item><title>Zabbix HA Cluster — Proxies + Database Cluster (IaC)</title><link>https://polar-node.work/projects/zabbix-ha-cluster/</link><pubDate>Fri, 19 Jun 2026 00:00:00 +0000</pubDate><guid>https://polar-node.work/projects/zabbix-ha-cluster/</guid><description>&lt;p&gt;&lt;strong&gt;Status: in progress.&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;A fully redundant Zabbix monitoring stack, deployed entirely through code rather than manual configuration:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Multi-node Zabbix server cluster&lt;/strong&gt; — native Zabbix HA nodes for server-level failover&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Distributed Zabbix proxies&lt;/strong&gt; — spread across network segments or regions for resilient, scalable data collection&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Clustered database backend&lt;/strong&gt; — the catalog/history database itself deployed as a cluster, not a single point of failure&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Infrastructure as Code&lt;/strong&gt; — the entire stack reproducible from a single set of Terraform/Ansible definitions&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;The goal is portability: the same IaC definitions should stand up the cluster identically whether the target is &lt;strong&gt;on-premise Proxmox VE&lt;/strong&gt;, or a public cloud — &lt;strong&gt;AWS&lt;/strong&gt;, &lt;strong&gt;Azure&lt;/strong&gt;, or &lt;strong&gt;GCP&lt;/strong&gt;. Same architecture, same automation, different provider underneath.&lt;/p&gt;</description></item></channel></rss>