2019-01-02 04:50:14 +00:00
|
|
|
# Backups
|
|
|
|
|
2019-01-05 02:22:48 +00:00
|
|
|
We're using [Ark][1] for backing up Kubernetes config and GKE resources. It is
|
|
|
|
available as a Git submodule in the `vendor/` folder (incl. the `ark`
|
|
|
|
executable).
|
|
|
|
|
2019-01-07 11:01:49 +00:00
|
|
|
In order to initialize and update submodules in your local repo, run once:
|
2019-01-05 02:22:48 +00:00
|
|
|
|
2019-01-07 11:01:49 +00:00
|
|
|
git submodule update --init
|
2019-01-05 02:22:48 +00:00
|
|
|
|
|
|
|
Then, to fetch/update the modules, run:
|
|
|
|
|
|
|
|
git submodule update
|
|
|
|
|
|
|
|
The Ark service is running on the Sidamo cluster and was set up using the
|
2019-01-05 03:23:17 +00:00
|
|
|
[official docs' GCP instructions and config files][4]. There's a daily backup
|
|
|
|
schedule in effect for Gitea (using the label `app=gitea`).
|
|
|
|
|
|
|
|
Please refer to Ark's [ Getting Started ][5] doc for all backup and restore
|
|
|
|
commands.
|
2019-01-02 04:50:14 +00:00
|
|
|
|
|
|
|
## Backup location
|
|
|
|
|
|
|
|
Cluster configuration (including all live resources) is backed up to [a Google
|
|
|
|
Cloud Storage container][3].
|
|
|
|
|
|
|
|
## Persistent volumes
|
|
|
|
|
|
|
|
Persistent volumes are just GCE disks. Thus, with the current config, Ark
|
|
|
|
creates volume snapshots as native [GCE disk snapshots][2].
|
|
|
|
|
|
|
|
[1]: https://heptio.github.io/ark/v0.10.0
|
|
|
|
[2]: https://console.cloud.google.com/compute/snapshots?organizationId=772167872692&project=fluted-magpie-218106&tab=snapshots&snapshotssize=50
|
|
|
|
[3]: https://console.cloud.google.com/storage/browser/sidamo-backups?project=fluted-magpie-218106&organizationId=772167872692
|
2019-01-05 02:22:48 +00:00
|
|
|
[4]: https://heptio.github.io/ark/v0.10.0/gcp-config
|
2019-01-05 03:23:17 +00:00
|
|
|
[5]: https://heptio.github.io/ark/v0.10.0/get-started
|