From cacb5f0eae0f2bd64d4f5b4de801d34aa7f10e4f Mon Sep 17 00:00:00 2001 From: Tiger Kaovilai Date: Fri, 9 Aug 2024 17:02:37 -0400 Subject: [PATCH] Apply suggestions from code review Signed-off-by: Tiger Kaovilai Signed-off-by: Tiger Kaovilai --- design/retry-patching-configuration_design.md | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-) diff --git a/design/retry-patching-configuration_design.md b/design/retry-patching-configuration_design.md index 3adacf93a..b8ddbb44f 100644 --- a/design/retry-patching-configuration_design.md +++ b/design/retry-patching-configuration_design.md @@ -1,7 +1,7 @@ # Backup Restore Status Patch Retrying Configuration ## Abstract -When a backup/restore completes, we want to ensure that the restore custom resource progress to the correct status. +When a backup/restore completes, we want to ensure that the custom resource progresses to the correct status. If a patch call fails to update status to completion, it should be retried up to a certain time limit. This design proposes a way to configure timeout for this retry time limit. @@ -105,5 +105,3 @@ Retry should only trigger a restore or backup that is already in progress and no ## Implementation There is a past implementation in [#7845](https://github.com/vmware-tanzu/velero/pull/7845/) where implementation for this design will be based upon. -## Open Issues -A discussion of issues relating to this proposal for which the author does not know the solution. This section may be omitted if there are none.