diff options
| author | Marcel Amirault <mamirault@gitlab.com> | 2019-08-21 09:53:06 +0000 |
|---|---|---|
| committer | Achilleas Pipinellis <axil@gitlab.com> | 2019-08-21 09:53:06 +0000 |
| commit | 8627131929293949ed1918b713fd947615f9743c (patch) | |
| tree | 2461958f4a67565ef7e0b35f0f4947ab25d2801f | |
| parent | 28d11071ceebe5a6e9de38f4462b12e7640da90a (diff) | |
| download | gitlab-ce-8627131929293949ed1918b713fd947615f9743c.tar.gz | |
Add let's encrypt omnibus guide link
| -rw-r--r-- | doc/administration/container_registry.md | 6 |
1 files changed, 5 insertions, 1 deletions
diff --git a/doc/administration/container_registry.md b/doc/administration/container_registry.md index c90a633ec5a..d43b3718bf9 100644 --- a/doc/administration/container_registry.md +++ b/doc/administration/container_registry.md @@ -172,9 +172,13 @@ docker login gitlab.example.com:4567 If the Registry is configured to use its own domain, you will need a TLS certificate for that specific domain (e.g., `registry.example.com`) or maybe -a wildcard certificate if hosted under a subdomain of your existing GitLab +a wildcard certificate if hosted under a subdomain of your existing GitLab domain (e.g., `registry.gitlab.example.com`). +NOTE: **Note:** +As well as manually generated SSL certificates (explained here), certificates automatically +generated by Let's Encrypt are also [supported in Omnibus installs](https://docs.gitlab.com/omnibus/settings/ssl.html#host-services). + Let's assume that you want the container Registry to be accessible at `https://registry.gitlab.example.com`. |