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

The "backup.ark.heptio.com/backup-volumes" setting for restic is unclear #568

Closed
trondhindenes opened this issue Jun 21, 2018 · 5 comments
Closed

Comments

@trondhindenes
Copy link

Not sure if this should point to the name of a pvc, the name of a volume, or the name of the mounted path inside the pod. Would be awesome to get that clarified

@trondhindenes
Copy link
Author

It would be great to get better logging of what ark expected to find, and what it didn't find. If there's an expected metadata annotation that is missing maybe log that out aswell. Reading the statement below its still not clear to me where the error is.

time="2018-06-21T22:02:52Z" level=error msg="backup failed" error="pod volume backup failed: error getting volume directory name: volume not found in pod" key=heptio-ark/nginx-example logSource="pkg/controller/backup_controller.go:280"

@skriss
Copy link
Contributor

skriss commented Jun 22, 2018

Good feedback. FYI this should be a comma-separated list of volume names.

@rosskukulinski
Copy link
Contributor

@skriss Marking this against the v0.9.0 milestone, let me know if that doesn't feel right to you.

Two action items I think:

  • Improve log output to aid debuggability
  • Improve documentation for the field and/or provide a Deployment manifest which has the inline annotation.

@skriss
Copy link
Contributor

skriss commented Jul 2, 2018

The documentation has been clarified. I'll tweak the log message before v0.9.0.

@skriss
Copy link
Contributor

skriss commented Jul 3, 2018

Actually improved logging has already been fixed as well, with #606. Closing this issue out, but please reach out if any further issues!

@skriss skriss closed this as completed Jul 3, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants