diff --git a/docs/upgrade/v1-2-2-to-v1-3-1.md b/docs/upgrade/v1-2-2-to-v1-3-1.md
index 140cd94a461..9810d79eddf 100644
--- a/docs/upgrade/v1-2-2-to-v1-3-1.md
+++ b/docs/upgrade/v1-2-2-to-v1-3-1.md
@@ -21,6 +21,11 @@ For air-gapped environments, see [Prepare an air-gapped upgrade](./automatic.md#
 
 ### 1. Cluster upgrade stuck after the first node is upgraded
 
+:::tip
+To prevent this issue from occurring, label the `local-kubeconfig` secret before starting the upgrade process. 
+`kubectl label secret local-kubeconfig -n fleet-local cluster.x-k8s.io/cluster-name=local`
+:::
+
 When upgrading a Harvester cluster from v1.2.2 or v1.3.0 to v1.3.1, the upgrade process becomes stuck after the first node is upgraded. 
 
 Example:
diff --git a/versioned_docs/version-v1.3/upgrade/v1-2-2-to-v1-3-1.md b/versioned_docs/version-v1.3/upgrade/v1-2-2-to-v1-3-1.md
index 140cd94a461..9810d79eddf 100644
--- a/versioned_docs/version-v1.3/upgrade/v1-2-2-to-v1-3-1.md
+++ b/versioned_docs/version-v1.3/upgrade/v1-2-2-to-v1-3-1.md
@@ -21,6 +21,11 @@ For air-gapped environments, see [Prepare an air-gapped upgrade](./automatic.md#
 
 ### 1. Cluster upgrade stuck after the first node is upgraded
 
+:::tip
+To prevent this issue from occurring, label the `local-kubeconfig` secret before starting the upgrade process. 
+`kubectl label secret local-kubeconfig -n fleet-local cluster.x-k8s.io/cluster-name=local`
+:::
+
 When upgrading a Harvester cluster from v1.2.2 or v1.3.0 to v1.3.1, the upgrade process becomes stuck after the first node is upgraded. 
 
 Example: