Velero: Manage the restic cache dir more effectively

[crdemon09]

/scratch/.cache/restic/restic-check-cache-* folder is too huge
Can we somehow disable a restic cache using velero?

Solution
velero restic --no-cache

Anything else you would like to add:
The size is growing up really quick while doing a schedule backup, with 4GB of neo4j database - I have /scratch folder in 2 days - 13G and then velero pod got "Evicted"

Environment:

• Velero version 1.0.0
• Kubernetes version 1.14
• Cloud provider or hardware configuration:
• OS CentOS

[crdemon09]

Small update - I think it's related to this #1659
Restic upon a crash - creating a restic-cache folder - making size inside a k8s pod growing up.

[skriss]

We don't currently have a way to disable the restic cache; you could consider mounting a PV into the velero pod to use for the scratch dir, instead of using an empty dir.

[Davidsod]

@skriss thanks for the answer. What would be the downsides in that case?

[skriss]

I don't think there are really any downsides apart from the cost of the persistent storage. It's possible that you'll still run into issues where the cache eventually exceeds the size of the PV - I'm not sure off the top of my head.

[eleanor-millman]

Closing because workaround exists.