From 0c4649c273efd26554e13832fb2262e0bd176958 Mon Sep 17 00:00:00 2001 From: Alex Seymour Date: Thu, 5 Feb 2026 15:05:01 +0100 Subject: [PATCH] Clarify outbound connectivity requirements for rancher-backup installation in air-gapped environments --- .../migrate-rancher-to-new-cluster.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/how-to-guides/new-user-guides/backup-restore-and-disaster-recovery/migrate-rancher-to-new-cluster.md b/docs/how-to-guides/new-user-guides/backup-restore-and-disaster-recovery/migrate-rancher-to-new-cluster.md index 284646372a0..b7176fe5746 100644 --- a/docs/how-to-guides/new-user-guides/backup-restore-and-disaster-recovery/migrate-rancher-to-new-cluster.md +++ b/docs/how-to-guides/new-user-guides/backup-restore-and-disaster-recovery/migrate-rancher-to-new-cluster.md @@ -50,7 +50,7 @@ Install the [`rancher-backup chart`](https://github.com/rancher/backup-restore-o :::note - The above assumes an environment with outbound connectivity to Docker Hub and to charts.rancher.io. + The above assumes an environment with outbound connectivity to Docker Hub. For an **air-gapped environment**, use the following Helm values to pull the `backup-restore-operator` and `kubectl` images from your private registry when you install the rancher-backup Helm chart.