From 7ac40f553a990fcdbbfa1bf3bf49eb514c79036d Mon Sep 17 00:00:00 2001 From: Tim Poffenbarger Date: Mon, 3 Feb 2020 22:27:32 +0000 Subject: [PATCH] clarify docs as to when TLS is used --- doc/ci/docker/using_docker_build.md | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/doc/ci/docker/using_docker_build.md b/doc/ci/docker/using_docker_build.md index 1635a3ffa36638..15335c9ba44b82 100644 --- a/doc/ci/docker/using_docker_build.md +++ b/doc/ci/docker/using_docker_build.md @@ -153,7 +153,7 @@ The Docker daemon supports connection over TLS and it's done by default for Docker 19.03.1 or higher. This is the **suggested** way to use the docker-in-docker service and [GitLab.com Shared Runners](../../user/gitlab_com/index.md#shared-runners) -support this. +have implemented this model. 1. Install [GitLab Runner](https://docs.gitlab.com/runner/install/). @@ -245,7 +245,8 @@ support this. Sometimes there are legitimate reasons why you might want to disable TLS. For example, you have no control over the GitLab Runner configuration -that you are using. +that you are using. The Runner installed via [GitLab Managed Apps](https://docs.gitlab.com/ee/user/clusters/applications.html#gitlab-runner) +on Kubernetes clusters has been implemented using this model. Assuming that the Runner `config.toml` is similar to: -- GitLab