<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Disaster-Recovery on Galust Arakelyan</title><link>https://galust-dev.ru/tags/disaster-recovery/</link><description>Recent content in Disaster-Recovery on Galust Arakelyan</description><generator>Hugo</generator><language>en</language><lastBuildDate>Sat, 24 Oct 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://galust-dev.ru/tags/disaster-recovery/index.xml" rel="self" type="application/rss+xml"/><item><title>Backing up a Kubernetes cluster whose nodes can't reach anything</title><link>https://galust-dev.ru/blog/velero-without-internet/</link><pubDate>Sat, 24 Oct 2026 00:00:00 +0000</pubDate><guid>https://galust-dev.ru/blog/velero-without-internet/</guid><description>&lt;p&gt;In October 2026 our cloud provider lost two of its three availability zones within a few days. The production cluster was still there, and its API server answered over VPN, but the surviving worker nodes had no internet access: the NAT gateway lived in a dead zone. The provider&amp;rsquo;s object storage was read-only.&lt;/p&gt;&#10;&lt;p&gt;We needed a full backup of the cluster before deciding where to restore it. The usual way is to install Velero into the cluster, but that was impossible here: nodes couldn&amp;rsquo;t pull the Velero image, and they couldn&amp;rsquo;t reach any object storage to write to.&lt;/p&gt;</description></item></channel></rss>