From 5e71d361f73a40ecd60e4a204298edbfddcdd063 Mon Sep 17 00:00:00 2001
From: BornChanger <97348524+BornChanger@users.noreply.github.com>
Date: Tue, 16 Jan 2024 17:49:02 +0800
Subject: [PATCH] Update
 en/restore-from-ebs-snapshot-across-multiple-kubernetes.md

---
 en/restore-from-ebs-snapshot-across-multiple-kubernetes.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/en/restore-from-ebs-snapshot-across-multiple-kubernetes.md b/en/restore-from-ebs-snapshot-across-multiple-kubernetes.md
index b97b26c12..7241868f5 100644
--- a/en/restore-from-ebs-snapshot-across-multiple-kubernetes.md
+++ b/en/restore-from-ebs-snapshot-across-multiple-kubernetes.md
@@ -15,7 +15,7 @@ The restore method described in this document is implemented based on CustomReso
 
 ## Limitations
 
-- Snapshot restore is applicable to TiDB Operator v1.5.1 or later versions and TiDB v6.5.4 or later versions.
+- Snapshot restore is applicable to TiDB Operator v1.5.2 or later versions and TiDB v6.5.8 or later versions.
 - You can use snapshot restore only to restore data to a cluster with the same number of TiKV nodes and volumes configuration. That is, the number of TiKV nodes and volume configurations of TiKV nodes are identical between the restore cluster and backup cluster.
 - Snapshot restore is currently not supported for TiFlash, TiCDC, DM, and TiDB Binlog nodes.