VolumePopulator & restic mover: Handling Uninitialized Restic Repositories in a GitOps Workflow

[sambartik]

Hello,

I am currently facing a slight hassle, and I am wondering if there is a way around this, the volsync way.

For my apps' PVC needs I define these resources:

• ReplicationDestination with a restic mover and Snapshot copy method without defined PVC
• PVC with VolumePopulator using the mentioned replication destination as source
• ReplicationSource with source PVC being the one mentioned right above, using Snapshot as the copy method

If I deploy these resources together all should work, granted that there was at least one backup earlier. I.e. the remote restic repository has been initialized before.

However, the problem occurs when I am defining a brand new PVC. Currently, the ReplicationDestination wouldnt be able to fetch anything since there is no remote repository, yet. And the VolumePopulator will keep the PVC stuck in pending as there is no Snapshot created by the ReplicationDestination.

Currently, the way I can work around this is to first manually create a PVC without VolumePopulator and set up the restic mover. Only after this point I can use VolumePopulator and set it up the way I described earlier.

This however breaks my GitOps workflow and introduces the need for manual interaction with my cluster to deploy the initial PVC.

Is there a better way I can do this? I.e. let the VolumePopulator initialize an empty PVC in case the remote restic repository was not initialized before?

Thanks!

[sambartik]

Indeed this appears to be the case and it works without initialized remote restic repo. This was a configurational mistake on my end, sorry.