kosmos/gitea.kosmos.org
kosmos
/
gitea.kosmos.org
Archived
8
1
Fork 0
Code Issues Pull Requests Releases Activity

Merge branch 'feature/ark_to_velero' of kosmos/gitea.kosmos.org into master

This commit is contained in:
Râu Cao 2019-06-22 12:26:30 +00:00 committed by Gitea
parent 9f4a5b452c a3fa72bb56
commit 1f6e0b7d57
3 changed files with 14 additions and 26 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

3
.gitmodules vendored
View File

@ -1,3 +0,0 @@
[submodule "vendor/ark"]
path = vendor/ark
url = git@github.com:heptio/ark.git

36
doc/backup-and-restore.md
View File

@ -1,36 +1,28 @@
# Backups # Backups
We're using [Ark][1] for backing up Kubernetes config and GKE resources. It is We're using [Velero][1] (formerly Ark) for backing up Kubernetes config and GKE
available as a Git submodule in the `vendor/` folder (incl. the `ark` resources. It is available as a compiled binary for your platform [on GitHub][2]
executable).
In order to initialize and update submodules in your local repo, run once: 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
git submodule update --init
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
[official docs' GCP instructions and config files][4]. There's a daily backup
schedule in effect for Gitea (using the label `app=gitea`). schedule in effect for Gitea (using the label `app=gitea`).
Please refer to Ark's [ Getting Started ][5] doc for all backup and restore Please refer to Velero's [ Getting Started ][4] doc for all backup and restore
commands. commands.
## Backup location ## Backup location
Cluster configuration (including all live resources) is backed up to [a Google Cluster configuration (including all live resources) is backed up to [a Google
Cloud Storage container][3]. Cloud Storage container][5].
## Persistent volumes ## Persistent volumes
Persistent volumes are just GCE disks. Thus, with the current config, Ark Persistent volumes are just GCE disks. Thus, with the current config, Velero
creates volume snapshots as native [GCE disk snapshots][2]. creates volume snapshots as native [GCE disk snapshots][6].
[1]: https://heptio.github.io/ark/v0.10.0 [1]: https://velero.io/docs/v1.0.0
[2]: https://console.cloud.google.com/compute/snapshots?organizationId=772167872692&project=fluted-magpie-218106&tab=snapshots&snapshotssize=50 [2]: https://github.com/heptio/velero/releases/tag/v1.0.0
[3]: https://console.cloud.google.com/storage/browser/sidamo-backups?project=fluted-magpie-218106&organizationId=772167872692 [3]: https://velero.io/docs/v1.0.0/gcp-config/
[4]: https://heptio.github.io/ark/v0.10.0/gcp-config [4]: https://velero.io/docs/v1.0.0/about/
[5]: https://heptio.github.io/ark/v0.10.0/get-started [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

1
vendor/ark vendored

@ -1 +0,0 @@
Subproject commit 0fd7872ef48ce617e561e6e45f8ccb0f11637f58