From ff634862b4b5b7b259f8033d4f33f375d92a74af Mon Sep 17 00:00:00 2001 From: lyndon-li <98304688+Lyndon-Li@users.noreply.github.com> Date: Tue, 2 Jul 2024 05:58:20 +0800 Subject: [PATCH] issue 7903: add a limitation clarification for waitForSingleConsumer PVC (#7948) Signed-off-by: Lyndon-Li --- changelogs/unreleased/7948-Lyndon-Li | 1 + site/content/docs/main/restore-reference.md | 2 ++ 2 files changed, 3 insertions(+) create mode 100644 changelogs/unreleased/7948-Lyndon-Li diff --git a/changelogs/unreleased/7948-Lyndon-Li b/changelogs/unreleased/7948-Lyndon-Li new file mode 100644 index 000000000..bf09edb35 --- /dev/null +++ b/changelogs/unreleased/7948-Lyndon-Li @@ -0,0 +1 @@ +Fix issue #7904, add the deprecation and limitation clarification for change PVC selected-node feature \ No newline at end of file diff --git a/site/content/docs/main/restore-reference.md b/site/content/docs/main/restore-reference.md index e4e3c7822..a7ec86e07 100644 --- a/site/content/docs/main/restore-reference.md +++ b/site/content/docs/main/restore-reference.md @@ -241,6 +241,8 @@ data: : ``` +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: