-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
Drop volumes matching name ServiceAccountName-token- #910
Drop volumes matching name ServiceAccountName-token- #910
Conversation
@james-powis I was thinking that this should go into Can you confirm there was another non-restic initContainer on the workload you had issues with? |
864b539
to
fa4c585
Compare
Signed-off-by: James Powis <[email protected]>
fa4c585
to
30369c2
Compare
@skriss You are right about that... And so it is, ready for your review, should be pretty easy it is nearly an identical duplication of the container volumeMount function and test. |
Also can I request a release after this is merged, even if it is a pre/beta release, I have a restore I need to perform.... |
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, thanks @james-powis!
@carlisia PTAL as well |
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.
👍 and thanks for adding a test!
Continuation of #843 and #840
Addresses #909
There does not appear to be a test file for the restic_restore_action.go file so this is one of those "this should not break anything, I hope..." I just don't know enough about this project (or go testing in general) to create a test file from scratch.
To that end it compiles, and in go that is a good sign.