summaryrefslogtreecommitdiff
path: root/doc/user
diff options
context:
space:
mode:
authorTiger <twatson@gitlab.com>2019-04-15 12:11:50 +1000
committerTiger <twatson@gitlab.com>2019-04-16 13:59:37 +1000
commite33ecfdec30a8efee191f8c2dd85ca54011128ce (patch)
tree9b97e13ff405e56add3a45ab1ce6ff4433e6e1d5 /doc/user
parent0a99e0220d9371423039f05f700af3675b26624f (diff)
downloadgitlab-ce-e33ecfdec30a8efee191f8c2dd85ca54011128ce.tar.gz
Disable JIT resource creation for project clusters60500-disable-jit-kubernetes-resource-creation-for-project-level-clusters
JIT resource creation blocks deployments if a user is self-managing their cluster, as it will fail the build if unable to create a namespace and service account. Using a custom namespace and service account was previously supported for project level clusters, so we should preserve this functionality. https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/27352
Diffstat (limited to 'doc/user')
-rw-r--r--doc/user/project/clusters/index.md4
1 files changed, 3 insertions, 1 deletions
diff --git a/doc/user/project/clusters/index.md b/doc/user/project/clusters/index.md
index 1983513174c..ccd60b9761f 100644
--- a/doc/user/project/clusters/index.md
+++ b/doc/user/project/clusters/index.md
@@ -565,7 +565,9 @@ service account of the cluster integration.
### Troubleshooting failed deployment jobs
GitLab will create a namespace and service account specifically for your
-deployment jobs, immediately before the jobs starts.
+deployment jobs. On project level clusters, this happens when the cluster
+is created. On group level clusters, resources are created immediately
+before the deployment job starts.
However, sometimes GitLab can not create them. In such instances, your job will fail with the message: