Michael Steven Fruchtman

@maciej-p The feature window closed on October 29 for 1.18. But I have tried to incorporate this into a code change since I need this locally anyway. Feel free to...

The kopia snapshots that have already finish will need to be marked for removal. Regular maintenance jobs take care of pruning after that.

I've dealt with this with kubevirt Virtualization which has a similar manner of spawning PVCs from VirtualMachine templates. Recent versions of Velero remove these on Restore automatically and preventing the...

Kopia will warn about excessive index blobs past 1000. Kopia can still handle it with enough resources. But never seen one that excessive even with 100 million+ unique blocks identified...

@kkavin Maintenance is triggered on a periodic schedule. The schedule is in the BackupRepository object for the (bsl, namespace, datamover type restic or kopia) combination under spec.maintenanceFrequency. In the Velero...

Unfortunately, kinda what I expected based on the description. Some maintain jobs are succeeding for smaller namespaces, but the job is running out resources for the larger one causing the...

@Gui13 You can submit per-PVC or user selectable scope of Kopia repositories as an enhancement request, but right now the kopia repo is shared across each namespace in the BSL....

@Sachin311098 Please check your BSL does not have an automatic expiration based on date-time. I've seen that before and kopia repositories are not compatible with automatic object expiration. Kopia maintenance...

I am not picky about how the change is exposed. Whether automatic by checking if the CSIDriver can provide this capabilities automatically or manual config; it will make no difference...

@sseago Yes, the spc_t is set the relabeling is disabled. The current spcNoRelabeling implementation in Velero requires readOnly to be set. Not all storage classes support ReadOnlyMany. topolvm has support...