<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>High-Availability on Kentrow</title><link>https://kentrow.fr/en/tags/high-availability/</link><description>Recent content in High-Availability on Kentrow</description><generator>Hugo -- gohugo.io</generator><language>en</language><copyright>© 2026 Kentrow</copyright><lastBuildDate>Fri, 18 Sep 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://kentrow.fr/en/tags/high-availability/index.xml" rel="self" type="application/rss+xml"/><item><title>My homelab from scratch (Part 11): high availability, Dokploy and two authorities for one resource</title><link>https://kentrow.fr/en/posts/mon-homelab-from-scratch-partie-11/</link><pubDate>Fri, 18 Sep 2026 00:00:00 +0000</pubDate><guid>https://kentrow.fr/en/posts/mon-homelab-from-scratch-partie-11/</guid><description>&lt;p>In &lt;a href="https://kentrow.fr/en/posts/mon-homelab-from-scratch-partie-10/" >part 10&lt;/a>, we built the base images and adopted a proper branch workflow. Right at the end, one question was left hanging: &lt;em>&amp;ldquo;if pve01 crashes, does the CI runner restart somewhere else?&amp;rdquo;&lt;/em> The answer was &lt;strong>no&lt;/strong>, and this &lt;strong>phase 5&lt;/strong> is the one that turns that &amp;ldquo;no&amp;rdquo; into &amp;ldquo;yes, in 1 min 14, proven with a stopwatch in hand&amp;rdquo;.&lt;/p></description><media:content xmlns:media="http://search.yahoo.com/mrss/" url="https://kentrow.fr/posts/mon-homelab-from-scratch-partie-11/feature.jpg"/></item></channel></rss>