issue 7903: add a limitation clarification for waitForSingleConsumer PVC (#7948)

Signed-off-by: Lyndon-Li <lyonghui@vmware.com>
2026-07-29 19:42:45 +00:00 · 2024-07-01 17:58:20 -04:00
parent 6a7f146aed
commit ff634862b4
2 changed files with 3 additions and 0 deletions
@@ -0,0 +1 @@
+Fix issue #7904, add the deprecation and limitation clarification for change PVC selected-node feature
@@ -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:
				`@@ -0,0 +1 @@`
				`Fix issue #7904, add the deprecation and limitation clarification for change PVC selected-node feature`