issue 7903: add a limitation clarification for waitForSingleConsumer …

…PVC (#7948) Signed-off-by: Lyndon-Li <lyonghui@vmware.com>
vmware-tanzu · Jul 1, 2024 · ff63486 · ff63486
1 parent 6a7f146
commit ff63486
Show file tree

Hide file tree

Showing 2 changed files with 3 additions and 0 deletions.
diff --git a/changelogs/unreleased/7948-Lyndon-Li b/changelogs/unreleased/7948-Lyndon-Li
@@ -0,0 +1 @@
+Fix issue #7904, add the deprecation and 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 is deprecated as of Velero 1.15, 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: