summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorTomasz Maczukin <tomasz@maczukin.pl>2018-04-05 16:43:52 +0200
committerTomasz Maczukin <tomasz@maczukin.pl>2018-04-05 16:43:52 +0200
commit9750006b1a7e78785256cf669c336c0075584d3b (patch)
tree97e72cb3cd84d8446f264e0760c40d69b71f65a4
parentb6d3e57d2a52f3d44b5840bd3ab53d3e811abeb3 (diff)
downloadgitlab-ce-9750006b1a7e78785256cf669c336c0075584d3b.tar.gz
Update documentation
-rw-r--r--doc/user/admin_area/settings/visibility_and_access_controls.md12
1 files changed, 9 insertions, 3 deletions
diff --git a/doc/user/admin_area/settings/visibility_and_access_controls.md b/doc/user/admin_area/settings/visibility_and_access_controls.md
index 633f16a617c..3d38588a9ed 100644
--- a/doc/user/admin_area/settings/visibility_and_access_controls.md
+++ b/doc/user/admin_area/settings/visibility_and_access_controls.md
@@ -32,9 +32,15 @@ When you choose to allow only one of the protocols, a couple of things will happ
On top of these UI restrictions, GitLab will deny all Git actions on the protocol
not selected.
+CAUTION: **Important:**
+Starting with [GitLab 10.7][ce-18021], HTTP(s) protocol will be allowed for
+git clone/fetch requests done by GitLab Runner from CI/CD Jobs, even if
+_Only SSH_ was selected.
+
> **Note:** Please keep in mind that disabling an access protocol does not actually
- block access to the server itself. The ports used for the protocol, be it SSH or
- HTTP, will still be accessible. What GitLab does is restrict access on the
- application level.
+block access to the server itself. The ports used for the protocol, be it SSH or
+HTTP, will still be accessible. What GitLab does is restrict access on the
+application level.
[ce-4696]: https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/4696
+[ce-18021]: https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/18021