Update volsync-target Docker tag to v0.5.0 #2674
Reference in New Issue
Block a user
Delete Branch "renovate/volsync-target-0.x"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
This PR contains the following updates:
0.3.0->0.5.0Release Notes
backube/volsync (volsync-target)
v0.5.0Compare Source
Added
volsync.backube/do-not-deleteto prevent VolSync from deleting them. Thisprovides 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.
Changed
Fixed
relationship file
request an incorrect size if the PVC capacity did not match the
requested size.
Security
Removed
ReplicationDestination
.status.conditions[]in favor of returning errors viathe "Synchronizing" Condition.
v0.4.0Compare Source
Added
LastSyncStartTimeto CRD statusChanged
NonetoDirectto make it more descriptive.snapshot.storage.k8s.io/v1beta1tosnapshot.storage.k8s.io/v1so that VolSync remains compatible w/ Kubernetes1.24+
snapshot.storage.k8s.io/v1Fixed
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Renovate Bot.