Backup-utility fails with ERROR: S3 error: 413 (Request Entity Too Large)

How to Use GitLab
1

Greetings, I’m trying to configure a backup for a GitLab installation (chart: gitlab/gitlab:3.3.13 ) for migration and the backup-utility process fails on the upload step with:

ERROR: S3 error: 413 (Request Entity Too Large)

The backup tar is created at /srv/gitlab/tmp/backup_tars and has a size of 320M. I think that the problem might be related to the minio ingress not accepting large files (even though the ingress has the annotation: client-max-body-size: "0" ), though these might as well be two separate problems.
gitlab-nginx-ingress-controller logs don’t show anything regarding a failed upload.
Any feedback on how to proceed is very welcome.
Thank you.

2

For anyone that might have a similar problem in the future, the problem proved out to be minio not being able to handle files larger than 145M. The solution based on https://gitlab.com/gitlab-org/charts/gitlab/blob/master/examples/values-external-objectstorage.yaml was to configure task-runner to use an external bucket.

gitlab:
  task-runner:
    replicas: 1
    backups:
      objectStorage:
        backend: gcs
        config:
          gcpProject: 
          secret: 
          key: