-
Notifications
You must be signed in to change notification settings - Fork 7
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
velero upgrade to v1.14.0 #619
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Have we tested this version for a successful backup and restore ? result success screenshot would've been nice.
* add e2e test for defect fix * fix upgrade * fix upgrade * add downgrade test * fix title
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The pipeline is failing on the YAML linters.
77dcf18
All commits have to be signed. |
* velero upgrade * update new velero crds * velero-plugin-for-aws version upgrade * Update node agent and velero crds for v1.14.0 * Remove node agent when performing AM upgrade (#627) * try removing older node agent * add namespace substitute to old path * fix replace * move check to AM * add var to modules * fix small error * fix check * add debug logging * try status fix * return fmt error * return fmt error * remove debugging lohs * fix lint * fix lint * gofumpt * prevent short circuit * add UT for AppMobilityVelero * Fix sanity e2e tests * Revert auth storage templates * Revert auth storage templates * Fix incorrect replace name for auth * Add e2e test (#629) * add e2e test for defect fix * fix upgrade * fix upgrade * add downgrade test * fix title * Migrate application mobility upgrade to scenarios file * Change config version * Fix application mobility e2e tests --------- Co-authored-by: Fernando Alfaro Campos <Fernando.Alfaro_campos@Dell.com> Co-authored-by: JacobGros <jacobgrosner4@gmail.com> Co-authored-by: abhi16394 <abhi.muralidhara@dell.com>
Description
velero upgrade to v1.14.0
Note: Due to the increase from velero v1.10.x to velero v1.14.0, the node-agent daemonset needs to be renamed to remove the application-mobility- prefix. This is due to a check within velero v1.14.0 when processing the restores (https://github.com/vmware-tanzu/velero/blob/2fc6300f2239f250b40b0488c35feae59520f2d3/pkg/podvolume/restorer.go#L119). After testing with those changes and updating the velero crds to match the latest v1.14.0, no issues were seen during testing.
Note: This partially fixes the running sanity tests.
GitHub Issues
List the GitHub issues impacted by this PR:
Checklist:
How Has This Been Tested?
Please describe the tests that you ran to verify your changes. Please also list any relevant details for your test configuration
sanity-results.txt