Lars Marowsky-Brée 😷<p>Unpopular opinion: if your use case requires (or even significantly benefits from) <a href="https://mastodon.online/tags/Linux" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Linux</span></a> <a href="https://mastodon.online/tags/Kernel" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Kernel</span></a> <a href="https://mastodon.online/tags/livepatching" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>livepatching</span></a>, your use case is mostly likely broken.</p><p>If you've got such high availability requirements, you likely should be running a 2-3 node cluster and focus on reducing switch-over latency.</p><p>In exchange, you'll get protection against many more issues than the limited number of available live patches.</p><p><a href="https://mastodon.online/tags/Dependability" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Dependability</span></a> <a href="https://mastodon.online/tags/HA" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>HA</span></a></p>