Open ricardomiguel-os opened 2 weeks ago
Could you provide below information for your case?
Hi @Lyndon-Li , yes sure.
For now we will increase the resources requests and limit
I've opened another issue for memory usage optimization in this case, see #7902
The behavior for preferred version has been there for a long time, so we will not change it unless there are many requirements. On the other hand, we will work on this issue on the original cause --- when there are many resources, the memory usage of velero backup looks unnecessarily high.
Hi @Lyndon-Li, thanks for the update. But do you think we still need those duplicated files for backward compatibility since this was added more than one year ago?
Describe the problem/challenge you have
Velero supports API group versions and for backward compatibility purposes, the backup files are being duplicated - 1 folder with version and another without version.
Here you can find that duplication.
Do you know if this duplication can be removed? The backup file size is increasing and the Velero pods are consuming a lot of memory on big clusters, triggering an OOMKilled when not configured with enough resources.
Describe the solution you'd like
Remove this condition or add it behind a feature flag.
Anything else you would like to add:
Environment:
velero version
): v1.9.3kubectl version
):/etc/os-release
):Vote on this issue!
This is an invitation to the Velero community to vote on issues, you can see the project's top voted issues listed here.
Use the "reaction smiley face" up to the right of this comment to vote.