S3 Artifacts

[arnaudguy]

Hello,

I’m running GitLab self-hosted on Cloudron, with self-hosted GitLab Runners on an external VPS.

Runners work fine (Docker executor), and CI cache is already stored on S3 at the runner level.

My question is about CI job artifacts storage:
• According to GitLab documentation, artifacts are stored by GitLab itself, not by the runner
• This requires enabling Object Storage (S3) in GitLab Omnibus configuration

Question

Does Cloudron officially support enabling S3 Object Storage for GitLab CI artifacts using GITLAB_OMNIBUS_CONFIG?

Example configuration (OVH / MinIO S3-compatible):

gitlab_rails['object_store']['enabled'] = true
gitlab_rails['object_store']['connection'] = {
  'provider' => 'AWS',
  'region'   => 'gra',
  'endpoint' => 'https://s3.gra.io.cloud.ovh.net',
  'path_style' => true,
  'aws_access_key_id' => 'XXX',
  'aws_secret_access_key' => 'XXX'
}
gitlab_rails['object_store']['objects']['artifacts']['bucket'] = 'gitlab-artifacts'

Additional questions:
• Is this configuration preserved across Cloudron updates?
• Are there any known limitations when using GitLab Object Storage on Cloudron?
• Is this the recommended approach, or is there a Cloudron-specific alternative?

Thanks in advance for your feedback.

[james]

Hello @arnaudguy

@arnaudguy said in S3 Artifacts:

Does Cloudron officially support enabling S3 Object Storage for GitLab CI artifacts using GITLAB_OMNIBUS_CONFIG?

Cloudron uses the config file, please see https://docs.cloudron.io/packages/gitlab/#custom-gitlabyml

@arnaudguy said in S3 Artifacts:

Is this configuration preserved across Cloudron updates?

If configured accordingly to the docs https://docs.gitlab.com/administration/object_storage/ and in /app/data/gitlab.yml yes, it is preserved across updates.

@arnaudguy said in S3 Artifacts:

Are there any known limitations when using GitLab Object Storage on Cloudron?

Not to our current knowledge. If you find any issues, please report them here.