In a schedule, the resultant backup goes in runtime go error.
the identical configuration works for other databases. The only difference is the database size is like 1.5Gb, the others are like 100/200Mb.
pod log attached.
the backup file is present in the restic repository after the execution, it seems all good. How to get rid of this error?
err.pod.log
Additional Context
It's a backup with prebackuppod, and the storage is private s3 endpoint.
Description
In a schedule, the resultant backup goes in runtime go error. the identical configuration works for other databases. The only difference is the database size is like 1.5Gb, the others are like 100/200Mb. pod log attached. the backup file is present in the restic repository after the execution, it seems all good. How to get rid of this error? err.pod.log
Additional Context
It's a backup with prebackuppod, and the storage is private s3 endpoint.
Logs
No response
Expected Behavior
to not have an error
Steps To Reproduce
No response
Version of K8up
v2.10.0
Version of Kubernetes
1.29
Distribution of Kubernetes
Kind