search

kubevirt / kubevirt-velero-plugin

Plugin to Velero which automates backing up and restoring KubeVirt/CDI objects
Apache License 2.0
29 stars 28 forks source link

Bump github.com/vmware-tanzu/velero from 1.9.3 to 1.10.0 #118

Closed dependabot[bot] closed 1 year ago

dependabot[bot] commented 1 year ago

Bumps github.com/vmware-tanzu/velero from 1.9.3 to 1.10.0.

Release notes

Sourced from github.com/vmware-tanzu/velero's releases.

v1.10.0

2022-11-29

Download

https://github.com/vmware-tanzu/velero/releases/tag/v1.10.0

Container Image

velero/velero:v1.10.0

Documentation

https://velero.io/docs/v1.10/

Upgrading

https://velero.io/docs/v1.10/upgrade-to-1.10/

Highlights

Unified Repository and Kopia integration

In this release, we introduced the Unified Repository architecture to build a data path where data movers and the backup repository are decoupled and a unified backup repository could serve various data movement activities.

In this release, we also deeply integrate Velero with Kopia, specifically, Kopia's uploader modules are isolated as a generic file system uploader; Kopia's repository modules are encapsulated as the unified backup repository.

For more information, refer to the design document.

File system backup refactor

Velero's file system backup (a.k.s. pod volume backup or formerly restic backup) is refactored as the first user of the Unified Repository architecture. Specifically, we added a new path, the Kopia path, besides the existing Restic path. While Restic path is still available and set as default, you can opt in Kopia path by specifying the uploader-type parameter at installation time. Meanwhile, you are free to restore from existing backups under either path, Velero dynamically switches to the correct path to process the restore.

Because of the new path, we renamed some modules and parameters, refer to the Break Changes section for more details.

For more information, visit the file system backup document and v1.10 upgrade guide document.

Meanwhile, we've created a performance guide for both Restic path and Kopia path, which helps you to choose between the two paths and provides you the best practice to configure them under different scenarios. Please note that the results in the guide are based on our testing environments, you may get different results when testing in your own ones. For more information, visit the performance guide document.

Plugin versioning V1 refactor

In this release, Velero moves plugins BackupItemAction, RestoreItemAction and VolumeSnapshotterAction to version v1, this allows future plugin changes that do not support backward compatibility, so is a preparation for various complex tasks, for example, data movement tasks. For more information, refer to the plugin versioning design document.

Refactor the controllers using Kubebuilder v3

In this release we continued our code modernization work, rewriting some controllers using Kubebuilder v3. This work is ongoing and we will continue to make progress in future releases.

Add credentials to volume snapshot locations

In this release, we enabled dedicate credentials options to volume snapshot locations so that you can specify credentials per volume snapshot location as same as backup storage location.

For more information, please visit the locations document.

CSI snapshot enhancements

In this release we added several changes to enhance the robustness of CSI snapshot procedures, for example, some protection code for error handling, and a mechanism to skip exclusion checks so that CSI snapshot works with various backup resource filters.

Backup schedule pause/unpause

In this release, Velero supports to pause/unpause a backup schedule during or after its creation. Specifically:

... (truncated)

Commits
  • 367f563 Merge pull request #5644 from Lyndon-Li/release-1.10
  • ebae88b rollback goreleaser upgrade
  • b5981f9 Merge pull request #5633 from danfengliu/cherry-pick-fix-git-action-issue-for...
  • 6288f3d Merge branch 'release-1.10' into cherry-pick-fix-git-action-issue-for-setup-g...
  • 4a8f676 Merge pull request #5632 from danfengliu/cherry-pick-fix-crd-verification-issue
  • 2981565 Cherry pick to 1.10 for Fix git action issue for setup-gcloud
  • 95d8134 Cherry pick to 1.10 Add verification for CRD installation
  • 0ea1c06 RC2 cut docs (#5624)
  • 623fac0 Merge pull request #5618 from reasonerjt/fix-api-doc-comment-1.10
  • ca8cbf8 Update the api-types doc
  • Additional commits viewable in compare view


Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
kubevirt-bot commented 1 year ago

Hi @dependabot[bot]. Thanks for your PR.

I'm waiting for a kubevirt member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.
ShellyKa13 commented 1 year ago

/ok-to-test

ShellyKa13 commented 1 year ago

/lgtm /approve

kubevirt-bot commented 1 year ago

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: ShellyKa13

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files: - ~~[OWNERS](https://github.com/kubevirt/kubevirt-velero-plugin/blob/main/OWNERS)~~ [ShellyKa13] Approvers can indicate their approval by writing `/approve` in a comment Approvers can cancel approval by writing `/approve cancel` in a comment