<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Haproxy on Pi Stack</title>
    <link>https://www.pistack.xyz/tags/haproxy/</link>
    <description>Recent content in Haproxy on Pi Stack</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Fri, 24 Apr 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.pistack.xyz/tags/haproxy/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Self-Hosted HAProxy Management: Data Plane API vs Prometheus Exporter vs Runtime API 2026</title>
      <link>https://www.pistack.xyz/posts/2026-04-24-haproxy-dataplane-api-vs-prometheus-exporter-vs-runtime-api-self-hosted-haproxy-management-guide-2026/</link>
      <pubDate>Fri, 24 Apr 2026 00:00:00 +0000</pubDate>
      <guid>https://www.pistack.xyz/posts/2026-04-24-haproxy-dataplane-api-vs-prometheus-exporter-vs-runtime-api-self-hosted-haproxy-management-guide-2026/</guid>
      <description>&lt;p&gt;HAProxy powers millions of production deployments as the world&amp;rsquo;s most widely-used open-source load balancer and reverse proxy. But managing it at scale — adding backends, checking stats, rotating SSL certs, and monitoring health — requires more than editing a static &lt;code&gt;haproxy.cfg&lt;/code&gt; file and sending &lt;code&gt;SIGHUP&lt;/code&gt;.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
