mirrors/velero
1
0
Fork 0
mirror of https://github.com/vmware-tanzu/velero.git synced 2026-08-15 19:56:06 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity

Add some description of update existing policy to state it works in a best-effort way. (#6856)

Browse Source 
Signed-off-by: Xun Jiang <jxun@vmware.com>
This commit is contained in:
Xun Jiang/Bruce Jiang
2023-09-22 14:18:42 -04:00
committed by GitHub
parent d3e5bb7451
commit 4bf87c01ea
5 changed files with 17 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files
site/content/docs/main/restore-reference.md
+3 -1
View File
@@ -269,7 +269,9 @@ are `none` (default) and `update`. If you choose to update existing resources du
You can also configure the existing resource policy in a [Restore](api-types/restore.md) object.
**NOTE:** Update of a resource only applies to the Kubernetes resource data such as its spec. It may not work as expected for certain resource types such as PVCs and Pods. In case of PVCs for example, data in the PV is not restored or overwritten in any way.
**NOTE:**
* Update of a resource only applies to the Kubernetes resource data such as its spec. It may not work as expected for certain resource types such as PVCs and Pods. In case of PVCs for example, data in the PV is not restored or overwritten in any way.
* `update` existing resource policy works in a best-effort way, which means when restore's `--existing-resource-policy` is set to `update`, Velero will try to update the resource if the resource already exists, if the update fails, Velero will fall back to the default non-destructive way in the restore, and just logs a warning without failing the restore.
## Removing a Restore object
site/content/docs/v1.10/restore-reference.md
+4
View File
@@ -224,6 +224,10 @@ You can change this policy for a restore by using the `--existing-resource-polic
You can also configure the existing resource policy in a [Restore](api-types/restore.md) object.
**NOTE:**
* Update of a resource only applies to the Kubernetes resource data such as its spec. It may not work as expected for certain resource types such as PVCs and Pods. In case of PVCs for example, data in the PV is not restored or overwritten in any way.
* `update` existing resource policy works in a best-effort way, which means when restore's `--existing-resource-policy` is set to `update`, Velero will try to update the resource if the resource already exists, if the update fails, Velero will fall back to the default non-destructive way in the restore, and just logs a warning without failing the restore.
## Removing a Restore object
There are two ways to delete a Restore object:
site/content/docs/v1.11/restore-reference.md
+3 -1
View File
@@ -267,7 +267,9 @@ You can change this policy for a restore by using the `--existing-resource-polic
You can also configure the existing resource policy in a [Restore](api-types/restore.md) object.
**NOTE:** Update of a resource only applies to the Kubernetes resource data such as its spec. It may not work as expected for certain resource types such as PVCs and Pods. In case of PVCs for example, data in the PV is not restored or overwritten in any way.
**NOTE:**
* Update of a resource only applies to the Kubernetes resource data such as its spec. It may not work as expected for certain resource types such as PVCs and Pods. In case of PVCs for example, data in the PV is not restored or overwritten in any way.
* `update` existing resource policy works in a best-effort way, which means when restore's `--existing-resource-policy` is set to `update`, Velero will try to update the resource if the resource already exists, if the update fails, Velero will fall back to the default non-destructive way in the restore, and just logs a warning without failing the restore.
## Removing a Restore object
site/content/docs/v1.12/restore-reference.md
+3 -1
View File
@@ -269,7 +269,9 @@ are `none` (default) and `update`. If you choose to update existing resources du
You can also configure the existing resource policy in a [Restore](api-types/restore.md) object.
**NOTE:** Update of a resource only applies to the Kubernetes resource data such as its spec. It may not work as expected for certain resource types such as PVCs and Pods. In case of PVCs for example, data in the PV is not restored or overwritten in any way.
**NOTE:**
* Update of a resource only applies to the Kubernetes resource data such as its spec. It may not work as expected for certain resource types such as PVCs and Pods. In case of PVCs for example, data in the PV is not restored or overwritten in any way.
* `update` existing resource policy works in a best-effort way, which means when restore's `--existing-resource-policy` is set to `update`, Velero will try to update the resource if the resource already exists, if the update fails, Velero will fall back to the default non-destructive way in the restore, and just logs a warning without failing the restore.
## Removing a Restore object
site/content/docs/v1.9/restore-reference.md
+4
View File
@@ -224,6 +224,10 @@ You can change this policy for a restore by using the `--existing-resource-polic
You can also configure the existing resource policy in a [Restore](api-types/restore.md) object.
**NOTE:**
* Update of a resource only applies to the Kubernetes resource data such as its spec. It may not work as expected for certain resource types such as PVCs and Pods. In case of PVCs for example, data in the PV is not restored or overwritten in any way.
* `update` existing resource policy works in a best-effort way, which means when restore's `--existing-resource-policy` is set to `update`, Velero will try to update the resource if the resource already exists, if the update fails, Velero will fall back to the default non-destructive way in the restore, and just logs a warning without failing the restore.
## Removing a Restore object
There are two ways to delete a Restore object: