Preserve volumeMounts from PodConfig

[ahyattdev]

Summary

Preserve volumeMounts from PodConfig.

This currently handled for Check and Prune, but not Backup, Archive, or Restore.

Issue mentioned here in a comment: #584 (comment)

One use case: if securityContext calls for a read only root FS, you need an emptyDir at /.cache for the restic cache to be written to.

Checklist

For Code changes

• Categorize the PR by setting a good title and adding one of the labels:
  bug, enhancement, documentation, change, breaking, dependency
  as they show up in the changelog
• PR contains the label area:operator
• Commits are signed off
• Link this PR to related issues
• I have not made any changes in the charts/ directory.

For Helm Chart changes

• Categorize the PR by setting a good title and adding one of the labels:
  bug, enhancement, documentation, change, breaking, dependency
  as they show up in the changelog
• PR contains the label area:chart
• PR contains the chart label, e.g. chart:k8up
• Commits are signed off
• Variables are documented in the values.yaml using the format required by Helm-Docs.
• Chart Version bumped if immediate release after merging is planned
• I have run make chart-docs
• Link this PR to related code release or other issues.

[ahyattdev]

Just saw #1056, which adds an emptyDir for /.cache by default now. That was my use case. So closing this PR.

[beniwtv]

I would still want this, for other use-cases. We use a CSI volume for secrets (for example, for S3), so being able to specify additional volumes to be included would still be beneficial.

[arska]

Thanks for this contribution! Preserving volumeMounts from PodConfig for Backup, Archive, and Restore makes a lot of sense — good catch that it was only handled for Check and Prune.

To move this forward, a couple of things are needed:

1. Rebase onto current master — the branch is a bit stale, which may be why full CI didn't trigger.

2. Sign off commits (DCO — Developer Certificate of Origin), which is a requirement for all CNCF projects. You can do both in one go:

git rebase --signoff master
git push --force-with-lease

If you have any questions, feel free to ask!