<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Relayd on Casey Robb</title><link>https://neozeon.io/tags/relayd/</link><description>Recent content in Relayd on Casey Robb</description><generator>Hugo</generator><language>en</language><lastBuildDate>Wed, 21 Oct 2026 08:46:18 -0600</lastBuildDate><atom:link href="https://neozeon.io/tags/relayd/index.xml" rel="self" type="application/rss+xml"/><item><title>Serving OpenShift VIPs from OpenBSD: relayd, pf, and unbound as Your Cluster's Load Balancer</title><link>https://neozeon.io/posts/ocp-relayd-unbound-pf/</link><pubDate>Sat, 17 Oct 2026 18:45:00 -0600</pubDate><guid>https://neozeon.io/posts/ocp-relayd-unbound-pf/</guid><description>&lt;h2 id="serving-openshift-vips-from-openbsd-relayd-pf-and-unbound"&gt;Serving OpenShift VIPs from OpenBSD: relayd, pf, and unbound&lt;/h2&gt;
&lt;p&gt;OpenShift is unusual among Kubernetes distros in how much it demands from your
network before it will install itself: three virtual IPs (API, internal API, and
wildcard ingress), DNS that resolves all three &lt;em&gt;before the first node boots&lt;/em&gt;,
and a healthcheck contract for your load balancer that is spelled out almost
to the millisecond in the install docs. In the cloud this is someone else&amp;rsquo;s
problem, on bare metal it is yours.&lt;/p&gt;</description></item></channel></rss>