Releases: backube/volsync
Releases · backube/volsync
Release v0.14.0
Changed
- Updated release to build on golang 1.24
- Syncthing updated to v1.30.0
- Rclone updated to v1.71.2
- Rclone --checksum, --transfers and --stats parameters can now be
overridden by RCLONE_ env vars in the rclone config secret - addition of moverVolumes for advanced users to allow mounting
of secrets or PVCs to their mover pod
Pre-release v0.14.0-rc.1
Changed
- Updated release to build on golang 1.24
- Syncthing updated to v1.30.0
- Rclone updated to v1.71.1
- Rclone --checksum, --transfers and --stats parameters can now be
overridden by RCLONE_ env vars in the rclone config secret - addition of moverVolumes for advanced users to allow mounting
of secrets or PVCs to their mover pod
Release v0.13.1
Fixed
- Increase timeout for issue with restic repository initialization
whenrestic cat configtakes > 10 seconds
Changed
- Minio used for e2e tests migrated to minio helm charts from bitnami
Release v0.13.0
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.7
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
Pre-release v0.13.0-rc.3
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.7
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
Pre-release v0.13.0-rc.2
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.6
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
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