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

Release v0.8.1

Changed

• Updated release to build on golang 1.21

Fixed

• Capture error on restic restore when connecting to repository

Release v0.8.0

Added

• Restic - ReplicationSource/ReplicationDestination can now specify a CustomCA
  that is from a configmap rather than only from a secret.
• Rclone - ReplicationSource/ReplicationDestination can now specify a CustomCA
  that is contained in either a configmap or secret.
• Restic - New option to run a restic unlock before the backup in the next sync.
• Restic - Allow passing through of RCLONE_ env vars from the restic secret to
  the mover job.
• Volume Populator added for ReplicationDestinations.

Changed

• Syncthing upgraded to v1.25.0
• Restic upgraded to v0.16.2
• Rclone upgraded to v1.63.1

Release v0.7.1

Changed

• Modified leader election settings (LeaseDuration, RenewDeadline, RetryPeriod)
  to match OpenShift recommendations
• Syncthing upgraded to v1.23.2

Fixed

• Updated the metrics service to use a unique pod selector (VolSync operator
  deployments only)

Release v0.7.0

Added

• New rsync-tls data mover that will replace the existing rsync-ssh mover
• moverServiceAccount parameter in the spec to allow advanced users to specify
  their own service account to be used by mover jobs/deploys

Changed

• VolSync now uses a single container image for the controller and all movers
• Rclone upgraded to v1.61.1
• Restic upgraded to v0.15.1
• Syncthing upgraded to v1.23.1

Fixed

• Syncthing should ignore lost+found directory

Security

• kube-rbac-proxy upgraded to 0.14.0
• All movers, except rsync-ssh, now run with reduced privileges by default (see docs)

Release v0.6.1

Fixed

• set HTTP_PROXY, HTTPS_PROXY, NO_PROXY env vars on mover pod if they are set on
  the controller. Allows for cluster-wide proxy usage.

Release v0.6.0

Added

• restic - allow passing in GOOGLE_APPLICATION_CREDENTIALS as a file

Changed

• ⚠️ Breaking change ⚠️ - Helm chart now manages VolSync CRDs
  directly.
  Upgrading the VolSync Helm chart from an earlier version will produce the
  following error:

  Error: UPGRADE FAILED: rendered manifests contain a resource that already exists. Unable to continue with update: CustomResourceDefinition "replicationdestinations.volsync.backube" in namespace "" exists and cannot be imported into the current release: invalid ownership metadata; label validation error: missing key "app.kubernetes.io/managed-by": must be set to "Helm"; annotation validation error: missing key "meta.helm.sh/release-name": must be set to "volsync"; annotation validation error: missing key "meta.helm.sh/release-namespace": must be set to "volsync-system"
  

  To fix, apply the missing labels and annotations as mentioned in the error
  message (your values may differ), then retry the upgrade:

  $ kubectl label crd/replicationdestinations.volsync.backube app.kubernetes.io/managed-by=Helm
  customresourcedefinition.apiextensions.k8s.io/replicationdestinations.volsync.backube labeled
  $ kubectl label crd/replicationsources.volsync.backube app.kubernetes.io/managed-by=Helm
  customresourcedefinition.apiextensions.k8s.io/replicationsources.volsync.backube labeled
  $ kubectl annotate crd/replicationdestinations.volsync.backube meta.helm.sh/release-name=volsync
  customresourcedefinition.apiextensions.k8s.io/replicationdestinations.volsync.backube annotated
  $ kubectl annotate crd/replicationsources.volsync.backube meta.helm.sh/release-name=volsync
  customresourcedefinition.apiextensions.k8s.io/replicationsources.volsync.backube annotated
  $ kubectl annotate crd/replicationdestinations.volsync.backube meta.helm.sh/release-namespace=volsync-system
  customresourcedefinition.apiextensions.k8s.io/replicationdestinations.volsync.backube annotated
  $ kubectl annotate crd/replicationsources.volsync.backube meta.helm.sh/release-namespace=volsync-system
  customresourcedefinition.apiextensions.k8s.io/replicationsources.volsync.backube annotated

• VolSync privileged mover SCC installed at startup on OpenShift

• Syncthing upgraded to 1.22.1

• Updates to build with golang 1.19

Fixed

• ReplicationSource fixes for rsync, rclone and restic to enable mounting
  ROX source PVCs as read-only

Security

• rclone mover updated to run with reduced privileges by default
• restic mover updated to run with reduced privileges by default
• syncthing mover updated to run with reduced privileges by default
• kube-rbac-proxy upgraded to 0.13.1

Release v0.5.2

Changed

• Updated release to build on golang 1.19 (except for the syncthing mover)
• remove deprecated io/ioutil and move to using functions in package os

Release v0.5.0

Added

• New data mover based on Syncthing for live data synchronization.
• Users can manually label destination Snapshot objects with volsync.backube/do-not-delete to prevent VolSync from deleting them. This provides a way for users to avoid having a Snapshot deleted while they are trying to use it. Users are then responsible for deleting the Snapshot.
• Publish Kubernetes Events to help troubleshooting

Changed

• Operator-SDK upgraded to 1.22.0
• Rclone upgraded to 1.59.0
• Restic upgraded to 0.13.1
• Syncthing upgraded to 1.20.1

Fixed

• Fix to RoleBinding created by VolSync for OCP namespace labeler.
• Fix to helm charts to remove hardcoded overwriting of pod security settings.
• Fix for node affinity (when using ReplicationSource in Direct mode) to use NodeSelector.
• Fixed log timestamps to be more readable.
• CLI: Fixed bug where previously specified options couldn't be removed from relationship file
• Fixed issue where a snapshot or clone created from a source PVC could request an incorrect size if the PVC capacity did not match the requested size.

Security

• kube-rbac-proxy upgraded to 0.13.0

Removed

• "Reconciled" condition removed from ReplicationSource and ReplicationDestination .status.conditions[] in favor of returning errors via the "Synchronizing" Condition.