Releases: backube/volsync
Releases · backube/volsync
Pre-Release v0.13.0-rc.1
Changed
- Multi-arch volsync image published in quay.io, will include amd64 as usual as well as arm64
- Restic updated to v0.18.0
- Syncthing updated to v1.29.5
Fixed
- Fix restic cache PVC name collision if replicationsource and
replicationdestination have the same name and are in the same
namespace
Security
- kube-rbac-proxy upgraded to v0.19.2
Release v0.12.1
Security
- Update golang.org/x/crypto to v0.36.0 for CVE-2025-22869
- Update golang.org/x/oauth2 to v0.28.0 for CVE-2025-22868
Release v0.12.0
Changed
- imagePullSecrets in helm charts will be copied from volsync controller
namespace to the mover namespace so mover jobs can use them - Updated release to build on golang 1.23
- Syncthing updated to v1.29.2
- kube-rbac-proxy image configurable in helm chart values
- mover scripts updated to use sync -f to only sync the target filesystem at
the end of mover tasks - Updates the ensure_initialized function in the restic mover script to
follow restic recommendations
Fixed
- All movers should return error if not able to EnsurePVCFromSrc
- Fix for mover job/service name length too long (>63 chars) if the
replicationsource or replicationdestination CR name is too long
Security
- kube-rbac-proxy upgraded to 0.18.2
Pre-Release v0.12.0-rc.1
Changed
- imagePullSecrets in helm charts will be copied from volsync controller
namespace to the mover namespace so mover jobs can use them - Updated release to build on golang 1.23
- Syncthing updated to v1.29.2
- kube-rbac-proxy image configurable in helm chart values
- mover scripts updated to use sync -f to only sync the target filesystem at
the end of mover tasks - Updates the ensure_initialized function in the restic mover script to
follow restic recommendations
Fixed
- All movers should return error if not able to EnsurePVCFromSrc
- Fix for mover job/service name length too long (>63 chars) if the
replicationsource or replicationdestination CR name is too long
Security
- kube-rbac-proxy upgraded to 0.18.2
Pre-Release v0.12.0-rc.1
Changed
- Syncthing updated to v1.28.1
- kube-rbac-proxy image configurable in helm chart values
- mover scripts updated to use sync -f to only sync the target filesystem at
the end of mover tasks - Updates the ensure_initialized function in the restic mover script to
follow restic recommendations
Fixed
- All movers should return error if not able to EnsurePVCFromSrc
Security
- kube-rbac-proxy upgraded to 0.18.1
Release v0.11.0
Changed
- Restic updated to v0.17.0
- Syncthing updated to v1.27.12
Added
- moverAffinity added to spec to allow for specifying the podAffinity assigned
to a VolSync mover pod - cleanupTempPVC option added for direct users to allow for deleting the
dynamically provisioned destination PVC after a completed replication. - cleanupCachePVC option for restic to allow for deleting the cache PVC
after a completed replication. - enableFileDeletion restic option to allow for restoring to an existing
PVC (for example running multiple restores) and delete files that do
not exist in the backup being restored.
Pre-Release v0.11.0-rc.1
Changed
- Restic updated to v0.17.0
- Syncthing updated to v1.27.12
Added
- moverAffinity added to spec to allow for specifying the podAffinity assigned to a VolSync mover pod
- cleanupTempPVC option added for direct users to allow for deleting the dynamically provisioned destination PVC
after a completed replication. - cleanupCachePVC option for restic to allow for deleting the cache PVC after a completed replication.
- enableFileDeletion restic option to allow for restoring to an existing PVC (for example running multiple restores)
and delete files that do not exist in the backup being restored.
Release v0.10.0
Fixed
- Fix for rsync-tls to handle replication when there are many files in the pvc root
- Fix for rsync-tls to handle files in the pvc root that start with
#
Changed
- Syncthing upgraded to v1.27.8
Added
- Debug mode for mover jobs added
Release v0.9.1
Fixed
- Allow restic restore from empty or non-initialized path
- Ignore lost+found on restic backup when checking for empty source volume
Release v0.9.0
Changed
- Syncthing upgraded to v1.27.3
- Restic upgraded to v0.16.4
- Updated release to build on golang 1.21
Added
- Allow customization of resource requirements and limits on mover job containers
- Include additional restic environment variables from the restic secret
(RESTIC_REST_USERNAME, RESTIC_REST_PASSWORD, AZURE_ENDPOINT_SUFFIX) - Copy trigger pvc annotations. Allows copy-trigger annotations on the pvc to
pause/trigger snapshots or clones in a sync - Include all RCLONE_ env vars from the rclone secret to be set in the rclone
mover job
Fixed
- Exclude lost+found for restic backups
- Check if ipv6 is enabled before assigning 'STUNNEL_LISTEN_PORT' in mover-rsync-tls
server script