Skip to content

Fix registry SSL certificate path defaults#3232

Open
Aoiujz wants to merge 1 commit intosameersbn:masterfrom
Aoiujz:fix-registry-ssl-default-paths
Open

Fix registry SSL certificate path defaults#3232
Aoiujz wants to merge 1 commit intosameersbn:masterfrom
Aoiujz:fix-registry-ssl-default-paths

Conversation

@Aoiujz
Copy link
Copy Markdown
Contributor

@Aoiujz Aoiujz commented Apr 8, 2026

Summary

  • stop falling back from SSL_REGISTRY_KEY_PATH to GITLAB_REGISTRY_KEY_PATH
  • stop falling back from SSL_REGISTRY_CERT_PATH to GITLAB_REGISTRY_CERT_PATH
  • keep the documented fixed defaults under /home/git/data/certs for the nginx registry TLS certificate and key

Why

GITLAB_REGISTRY_KEY_PATH is used for the authentication key pair between GitLab and the registry. It should not also become the implicit source for the nginx TLS certificate path used to proxy the registry externally.

The previous fallback chain mixed these two concerns and could cause the registry proxy to pick up the internal auth key path when SSL_REGISTRY_* was not configured. This change makes the runtime behavior match the documented defaults and keeps the internal auth certificate path separate from the external nginx TLS certificate path.

Testing

  • reviewed the resulting diff in assets/runtime/env-defaults
  • verified there are no file-level errors reported for the updated runtime defaults file

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant