issue 7903: add a limitation clarification for waitForSingleConsumer PVC

Signed-off-by: Lyndon-Li <[email protected]>
vmware-tanzu · Jun 28, 2024 · c0c20d2 · c0c20d2
1 parent c827fd0
commit c0c20d2
Showing 1 changed file with 2 additions and 0 deletions.
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 is being deprecated by following Velero deprecation policy. This feature is primarily used to remedy some problems in old Kubernetes versions as described [here](https://github.com/vmware-tanzu/velero/pull/2377). It may not work with the new features of Kubernetes and Velero. E.g., it 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: