- 1. Definition
- 2. Data flow
- 3. Proposal
- 4. Evaluation
- 4.1. Pros
- 4.2. Cons
This document is a work-in-progress and represents a very early state of the Pods design. Significant aspects are not documented, though we expect to add them in the future. This is one possible architecture for Pods, and we intend to contrast this with alternatives before deciding which approach to implement. This documentation will be kept even if we decide not to implement this so that we can document the reasons for not choosing this approach.
Each pods will take its own backups, and consequently have its own isolated backup / restore procedure.
GitLab Backup takes a backup of the PostgreSQL database used by the application, and also Git repository data.
Each pod has a number of application databases to back up (e.g.
Additionally, there may be cluster-wide metadata tables (e.g.
which is directly accesible via PostgreSQL.
It is currently unknown how cluster-wide metadata tables will be accessible. We may choose to have cluster-wide metadata tables backed up separately, or have each pod back up its copy of cluster-wide metdata tables.
As each pod will communicate with each other via API, and there will be no joins to the users table, it should be acceptable for each pod to take a backup independently of each other.
We can require that each pod take a snapshot for the PostgreSQL databases at around the same time to allow for a consistent-enough backup.
As the number of pods increases, it will likely not be feasible to take a snapshot at the same time for all pods. Hence taking backups independently is the better option.