Skip to content

Conversation

@maismail
Copy link
Contributor

@maismail maismail commented Nov 24, 2025

- 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:
Copy link
Contributor

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"

Copy link
Contributor Author

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"
Copy link
Contributor

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?

Copy link
Contributor Author

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

@maismail maismail enabled auto-merge (squash) December 19, 2025 20:05
@maismail maismail merged commit 3f553bc into logicalclocks:main Dec 19, 2025
1 check passed
@maismail maismail deleted the CLOUD-785 branch December 19, 2025 20:47
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants