-
Notifications
You must be signed in to change notification settings - Fork 28
[CLOUD-785] Rewrite backups page #531
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
Conversation
| - Ensure that Velero is installed and configured with the AWS plugin as described in the [prerequisites](#prerequisites). | ||
| - Set up a [Velero backup storage location](https://velero.io/docs/v1.17/api-types/backupstoragelocation/) to point to the S3 bucket. | ||
|
|
||
| - If you are using AWS S3: |
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.
Maybe extend with something like "If you are using AWS S3 and access is controlled by an IAM role"
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.
done
| enabled: true | ||
| schedule: "@weekly" | ||
| restoreFromBackup: | ||
| backupId: "254811200" |
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.
I suppose there is a way to find the backup ID by getting the Velero backups? Can you show an example before this?
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.
yeah, done, added the info at the end of velero backup restore. Although i would imaging this to be better planned as well before termintaing the cluster so it should be visible from the UI
Fixes https://hopsworks.atlassian.net/browse/CLOUD-785
Fixes https://hopsworks.atlassian.net/browse/HWORKS-2433