Backing up a GitLab installation

GitLab backups are taken by running the backup-utility command on the task-runner pod provided in the chart. Backups can also be automated by enabling the Cron based backup functionality of this chart.

Before running the backup for the first time, you should ensure the task-runner is properly configured for access to object storage

Follow these steps for backing up a GitLab Helm chart based installation

Create the backup

  1. Ensure the task runner pod is running, by executing the following command

    $ kubectl get pods -lrelease=RELEASE_NAME,app=task-runner
    
  2. Run the backup utility

    $ kubectl exec <task-runner pod name> -it backup-utility
    
  3. Visit the gitlab-backups bucket in the object storage service and ensure a tarball has been added. It will be named in <timestamp>_<version>_gitlab_backup.tar format.

  4. This tarball is required for restoration.

Cron based backup

Cron based backups can be enabled in this chart to happen at regular intervals as defined by the Kubernetes schedule.

You need to set the following parameters:

  • gitlab.task-runner.backups.cron.enabled: Set to true to enable cron based backups
  • gitlab.task-runner.backups.cron.schedule: Set as per the Kubernetes schedule docs
  • gitlab.task-runner.backups.cron.extraArgs: Optionally set extra arguments for backup-utility (like --skip db)

Backup the secrets

You should also save a copy of the rails secrets. (These are not included in the backup as a security precaution. We recommend keeping your full backup that includes the database separate from the copy of the secrets.)

  1. Find the object name for the rails secrets

    $ kubectl get secrets | grep rails-secret
    
  2. Save a copy of the rails secrets

    $ kubectl get secrets <rails-secret-name> -o jsonpath="{.data['secrets\.yml']}" | base64 --decode > secrets.yaml
    
  3. Store secrets.yml in a secure location, you may need it to fully restore your backups.

Additional Information