Feature Request: Private CA certificate handling for private registries

Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.

• Close this issue

Hi, my request comes about as a result of the issues I had getting the CI runner to push a built container back to the gitlab registry after a build success. I documented that issue gitlab-org/gitlab-ci-multi-runner#1350.

What I think would be useful is:

• Enable gitlab to record the CA certificate for private registries. (So perhaps it is a gitlab.rb configuration item?) I currently use gitlab as a container, and am using my own NGINX (not gitlab's NGINX in the container).
• With gitlab having the CA certificate, pass that to the CI runner, so that it is used during the build process (if required), so that a build can push built images back to the registry. (Avoiding the need to create custom docker build images, as I have explained in my issue report gitlab-org/gitlab-ci-multi-runner#1350
• Display and/or enable the CA certificate to be downloaded from the projects /.../container_registry URL, so if anybody wants to pull the built image, they can access and install the CA certificate to avoid the x509: certificate signed by unknown authority error.

...deon