Need a fature to retry backup in the backup pod for a specified number of times before abandoing the pod.

Description

Currently, the backup is attempted at the entry point, and the pod is abandoned if the attempt fails. Then, the Operator creates another pod and attempts the same. This may not work in all k8s environments because there could be delay in establishing communication with API. Practically 3 to 5 seconds delay is observed by users.

This is a feature request to consider a design change where backups are attempted using the same pod instead of a separate pod.

This would be a better solution than K8SPG-615

Environment

None

AFFECTED CS IDs

CS0047481

Activity

Julio Pasinatto January 28, 2025 at 1:04 PM

Verified.

Slava Sarzhan January 2, 2025 at 3:46 PM

Now it is possible to change backoffLimit and restartPolicy for backup jobs via cr using the following options:

Done

Details

Assignee

Reporter

Labels

Needs QA

Yes

Needs Doc

Yes

Story Points

Components

Sprint

Fix versions

Affects versions

Priority

Smart Checklist

Created August 8, 2024 at 7:01 AM
Updated March 17, 2025 at 5:49 PM
Resolved March 11, 2025 at 6:48 PM