issue 7904:and limitation clarification for change PVC selected-node …

…feature Signed-off-by: Lyndon-Li <[email protected]>
vmware-tanzu · Jun 28, 2024 · 4056a96 · 4056a96
1 parent 583cd8b
commit 4056a96
Show file tree

Hide file tree

Showing 2 changed files with 3 additions and 0 deletions.
diff --git a/changelogs/unreleased/7949-Lyndon-Li b/changelogs/unreleased/7949-Lyndon-Li
@@ -0,0 +1 @@
+Fix issue #7904, add the limitation clarification for change PVC selected-node feature
diff --git a/site/content/docs/main/restore-reference.md b/site/content/docs/main/restore-reference.md
@@ -241,6 +241,8 @@ data:
   <old-node-name>: <new-node-name>
 ```
 
+Note: This feature doesn't work for PVCs with ```WaitForFirstConsumer``` as the ```volumeBindingMode```. These kind of PVCs won't be bound until the pod is scheduled and the scheduler will overwrite the selected-node annotation to the node where the pod is scheduled to.  
+
 ## Restoring into a different namespace
 
 Velero can restore resources into a different namespace than the one they were backed up from. To do this, use the `--namespace-mappings` flag: