Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[2] Upgrade Velero chart #2031

Closed
3 of 8 tasks
AlbinB97 opened this issue Mar 1, 2024 · 2 comments · Fixed by #2121
Closed
3 of 8 tasks

[2] Upgrade Velero chart #2031

AlbinB97 opened this issue Mar 1, 2024 · 2 comments · Fixed by #2121
Assignees
Labels
kind/improvement Improvement of existing features, e.g. code cleanup or optimizations.

Comments

@AlbinB97
Copy link
Contributor

AlbinB97 commented Mar 1, 2024

Chart to upgrade

vmware-tanzu/velero

Reason for upgrade

  • Security patching
  • Upgrade to allow new features
  • Upgrade to prevent future issues
  • Other - Write the reason below

Additional context

Velero has been updated to fix CVEs. There's also some new features that could be useful, take a look at the changes here: https://github.com/vmware-tanzu/velero/releases

Acceptance criteria

  • I checked the migration of the new chart version:
    • The upgrade does not require migration steps
    • The upgrade requires migration steps
  • I tested the functionality of the new chart version:
    • The upgrade does not change current functionality
    • The upgrade changes current functionality
@AlbinB97 AlbinB97 added the kind/improvement Improvement of existing features, e.g. code cleanup or optimizations. label Mar 1, 2024
@Elias-elastisys
Copy link
Contributor

Please make sure to upgrade to at least version v1.13.1 to allow for Volume Snapshots and Velero snapshot data movement (arch topic: https://github.com/elastisys/ck8s-arch/issues/151)

@Ajarmar Ajarmar changed the title Upgrade Velero chart [2] Upgrade Velero chart May 6, 2024
@anders-elastisys anders-elastisys self-assigned this May 6, 2024
@anders-elastisys
Copy link
Contributor

anders-elastisys commented May 14, 2024

@Elias-elastisys as there was no chart released using Velero version v1.13.1, my PR currently use v1.13.0. So if this is still needed I suggest that we either add templating for overriding the image version, or we update the chart once this version is released.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/improvement Improvement of existing features, e.g. code cleanup or optimizations.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants