29 lines
1.2 KiB
Markdown
29 lines
1.2 KiB
Markdown
# Backups
|
|
|
|
We're using [Velero][1] (formerly Ark) for backing up Kubernetes config and GKE
|
|
resources. It is available as a compiled binary for your platform [on GitHub][2]
|
|
|
|
The Velero service is running on the Sidamo cluster and was set up using the
|
|
[official docs' GCP instructions][3]. There's a daily backup
|
|
schedule in effect for Gitea (using the label `app=gitea`).
|
|
|
|
Please refer to Velero's [ Getting Started ][4] doc for all backup and restore
|
|
commands.
|
|
|
|
## Backup location
|
|
|
|
Cluster configuration (including all live resources) is backed up to [a Google
|
|
Cloud Storage container][5].
|
|
|
|
## Persistent volumes
|
|
|
|
Persistent volumes are just GCE disks. Thus, with the current config, Velero
|
|
creates volume snapshots as native [GCE disk snapshots][6].
|
|
|
|
[1]: https://velero.io/docs/v1.0.0
|
|
[2]: https://github.com/heptio/velero/releases/tag/v1.0.0
|
|
[3]: https://velero.io/docs/v1.0.0/gcp-config/
|
|
[4]: https://velero.io/docs/v1.0.0/about/
|
|
[5]: https://console.cloud.google.com/storage/browser/sidamo-backups-new?project=fluted-magpie-218106&organizationId=772167872692
|
|
[6]: https://console.cloud.google.com/compute/snapshots?organizationId=772167872692&project=fluted-magpie-218106&tab=snapshots&snapshotssize=50
|