Backup to different object storage than Minio

Summary

When having minio enabled and having the cron backup configured to a different object storage the Buckets in Minio gets skipped during Backup.

Steps to reproduce

Just apply the configuration below. Most importantly have default minio configuration and then configure an offsite backup cron scheduler.

Configuration used

The relevant parts is that we have a task-runner configured with backup and the config is to an offsite s3 storage and then we have the default minio configuration.

  task-runner:
    backups:
      cron:
        enabled: true
        concurrencyPolicy: Forbid
        failedJobsHistoryLimit: 1
        schedule: "0 4 * * *"
        successfulJobsHistoryLimit: 3
        resources:
          limits:
            cpu: 1
            memory: 2G
          requests:
            cpu: 50m
            memory: 350M
        persistence:
          enabled: true
          storageClass: "hdd"
          accessMode: ReadWriteOnce
          size: 500Gi
      objectStorage:
        backend: s3
        config: 
          secret: gitlab-backup-s3cfg
          key: config

Current behavior

The object storage is skipped from backup. Due to the fact that the backup is trying to fetch the gitlab buckets in the remote object storage instead of the local one.

Expected behavior

I would like for the object storage to be part of the backup.

Versions

• Chart: 2.3.12 checking the master branch of the backup-utility script and the way the chart is configured it looks like it is the same issue in latest version.
• Platform:
  • Self-hosted: OpenStack
• Kubernetes: 1.3.9 (same for client and server
• Helm: 2.12.3 (same for client and server

Relevant logs

Bucket not found: registry. Skipping backup of registry ...
Bucket not found: gitlab-uploads. Skipping backup of uploads ...
Bucket not found: gitlab-artifacts. Skipping backup of artifacts ...
Bucket not found: git-lfs. Skipping backup of lfs ...
Bucket not found: gitlab-packages. Skipping backup of packages ...