Ability to disable the registry service (but not the feature)
Description including problem, use cases, benefits, and/or goals
I might have missed some configuration parameters, but it doesn't seem possible to use gitlab as a registry auth service (endpoint) without having the registry running on the gitlab host.
In some setups, it might be useful to have distincts gitlab and registry servers (more storage on the registry, or more close to the docker daemon in the network, with better throughput, ...).
Actually it is possible to configure an external registry, but the embedded one would still have to be enabled.
I found out it is possible to disable the nginx frontend, and that is a good start : registry_nginx['enable'] = false
What we are missing (but once again I might have missed some options), is the possibility to disable the local registry service. The actual registry['enable'] = false parameter disables the service, but also the feature (no "Container Registry" in the project, no auth).
Proposal
Provide a way through omnibus to disable the registry service without disabling the container registry feature to allow the usage of an external registry (which have to be installed and setted up manually or by other means than omnibus, of course).