diff options
author | Tiger <twatson@gitlab.com> | 2019-06-12 09:44:18 +1000 |
---|---|---|
committer | Tiger <twatson@gitlab.com> | 2019-06-18 12:43:52 +1000 |
commit | 74702f0e0e05bc346338fbd11b596fcbedfbaea6 (patch) | |
tree | e426ab17b7dc425c9d63dc9670b865fcbd17bb02 /doc | |
parent | db9ef69272155b3c8ead5c0e7d027bda2b623d43 (diff) | |
download | gitlab-ce-60617-enable-project-cluster-jit.tar.gz |
Enable project-level JIT resource creation60617-enable-project-cluster-jit
Previously this behaviour was only available to group
and instance-level clusters, as some project clusters
relied on Kubernetes credentials being passed through
to the runner instead of having their resources managed
by GitLab (which is not available when using JIT). These
clusters have been migrated to unmanaged, so resources
can be created on demand for the remaining managed clusters.
Diffstat (limited to 'doc')
-rw-r--r-- | doc/user/project/clusters/index.md | 4 |
1 files changed, 1 insertions, 3 deletions
diff --git a/doc/user/project/clusters/index.md b/doc/user/project/clusters/index.md index 181b20dc710..1a2c9cbc838 100644 --- a/doc/user/project/clusters/index.md +++ b/doc/user/project/clusters/index.md @@ -518,9 +518,7 @@ service account of the cluster integration. ### Troubleshooting failed deployment jobs GitLab will create a namespace and service account specifically for your -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. +deployment jobs. This happens immediately before the deployment job starts. However, sometimes GitLab can not create them. In such instances, your job will fail with the message: |