Gitlab Registry Helm Chart configuration

How to Use GitLab
1

:hugs: Please help fill in this template with all the details to help others help you more efficiently. Use formatting blocks for code, config, logs and ensure to remove sensitive data.

Problem to solve

Describe your question in as much detail as possible:
Failing to configure registry with S3 storage via K8s Helm Charts. A secret with S3 credentials is created and referred to via helm values.

storage:
s3:
accesskey:
secretkey:
bucket: gitlab-registry
region: us-east-1
regionendpoint:
forcepathstyle: true
v4Auth: true

Registry snippet from values:

registry:
  enabled: true
  storage:
    secret: registry-storage-secret
    key: config
  • What are you seeing, and how does that differ from what you expect to see?
    Continuously getting this error in registry pods
  • {“level”:“fatal”,“msg”:“configuring application: StorageDriver not registered: storage”,“time”:“2025-01-17T19:31:20.780Z”}
  • Consider including screenshots, error messages, and/or other helpful visuals

Steps to reproduce

Which troubleshooting steps have you already taken? Can you link to any docs or other resources so we know where you have been?

Configuration

Provide screenshots from the GitLab UI showing relevant configuration, if applicable.
On self-managed instances, add the relevant configuration settings or changes.

Versions

Helm Version: v7.3.9
Please add an x whether options apply, and add the version information.

  • Self-managed
  • GitLab.com SaaS
  • Dedicated

Versions

  • GitLab (Web: /help or self-managed system information sudo gitlab-rake gitlab:env:info):

Helpful resources

  1. Check the FAQ for helpful documentation, issues/bugs/feature proposals, and troubleshooting tips.
  2. Before opening a new topic, make sure to search for keywords in the forum search
  3. Check the GitLab project for existing issues. If you encounter a bug, please create a bug report issue.
  4. Review existing troubleshooting docs.

Thanks for taking the time to be thorough in your request, it really helps! :blush:

2

I was able to fix it already. The secret needs to be defined as below and not as storage.s3.

s3:
accesskey:
secretkey:
bucket: gitlab-registry
region: us-east-1
regionendpoint:
forcepathstyle: true
v4Auth: true