Renovate Bot
2ed60a2759
This PR contains the following updates: | Package | Update | Change | |---|---|---| | [volsync-target](https://github.com/backube/volsync) | minor | `0.3.0` -> `0.5.0` | --- ### Release Notes <details> <summary>backube/volsync (volsync-target)</summary> ### [`v0.5.0`](https://github.com/backube/volsync/blob/HEAD/CHANGELOG.md#050) [Compare Source](https://github.com/backube/volsync/compare/v0.4.0...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. ### [`v0.4.0`](https://github.com/backube/volsync/blob/HEAD/CHANGELOG.md#040---2022-05-12) [Compare Source](https://github.com/backube/volsync/compare/v0.3.0...v0.4.0) ##### Added - Helm: Add ability to specify container images by SHA hash - Started work on new CLI (kubectl plugin) - Support FIPS mode on OpenShift - Added additional field `LastSyncStartTime` to CRD status ##### Changed - Rename CopyMethod `None` to `Direct` to make it more descriptive. - Upgrade OperatorSDK to 1.15 - Move Rclone and Rsync movers to the Mover interface - Switch snapshot API version from `snapshot.storage.k8s.io/v1beta1` to `snapshot.storage.k8s.io/v1` so that VolSync remains compatible w/ Kubernetes 1.24+ - Minimum Kubernetes version is now 1.20 due to the switch to `snapshot.storage.k8s.io/v1` ##### Fixed - Resources weren't always removed after each sync iteration </details> --- ### 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. --- - [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this box --- This PR has been generated by [Renovate Bot](https://github.com/renovatebot/renovate). <!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiI0Mi4zOS4xIiwidXBkYXRlZEluVmVyIjoiNDIuMzkuMSIsInRhcmdldEJyYW5jaCI6Im1haW4iLCJsYWJlbHMiOlsiaW1hZ2UiXX0=--> Reviewed-on: #2674 Co-authored-by: Renovate Bot <renovate-bot@alexlebens.net> Co-committed-by: Renovate Bot <renovate-bot@alexlebens.net>