-
Notifications
You must be signed in to change notification settings - Fork 51
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
Changes to support velero 1.10 #500
Conversation
f02d641
to
231a5b1
Compare
231a5b1
to
c8d90ee
Compare
Sorry, some of the pre-check tests are failing for this PR ! Please check the Jenkins job for more details |
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.
Do we need to push vendor/ folder to the repo?
It was not a part of .gitignore in the past, so I assume it's expected. |
We don't have a vendor folder. I don't think we should start having this in the github. Can you add /vendor to .gitignore? |
c8d90ee
to
5c7d2fc
Compare
Fixed, removed the vendor, and added it as a part of gitignore. |
Sorry, some of the pre-check tests are failing for this PR ! Please check the Jenkins job for more details |
Please also update the document: |
Signed-off-by: Deepak Kinni <dkinni@vmware.com>
5c7d2fc
to
48069a4
Compare
Done. |
Sorry, some of the pre-check tests are failing for this PR ! Please check the Jenkins job for more details |
@deepakkinni With or without specifying default-volumes-to-fs-backup, the logs look identical. So what is the difference there? What does |
From the plugin's perspective, the primary change is The primary goal of the restic support is to ensure that specific volumes are skipped from backup. This is done by annotating the pod (https://velero.io/docs/v1.10/file-system-backup/#to-back-up). When When |
Can you add one test:
|
Clarified this in testing. |
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
Changes to support velero 1.10 Signed-off-by: Deepak Kinni <dkinni@vmware.com>
What this PR does / why we need it:
Changes to support velero 1.10
Updated to go 1.18
Testing
Build/Unit
Backup:
Without specifying default-volumes-to-fs-backup with annotation on the Pod
With specifying default-volumes-to-fs-backup and no annotation on the Pod
No annotation on the pod and without specifying default-volumes-to-fs-backup
Which issue(s) this PR fixes:
Fixes #485
Special notes for your reviewer:
Does this PR introduce a user-facing change?:
Signed-off-by: Deepak Kinni dkinni@vmware.com