summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorMayra Cabrera <mcabrera@gitlab.com>2018-03-09 09:39:32 +0000
committerAchilleas Pipinellis <axil@gitlab.com>2018-03-09 09:39:32 +0000
commitf01ca6dd804746e29d4a9cfdbfb4476870792de6 (patch)
treec1410e7059d6163f736a11edc7dca1083a668ccc
parent92e119859d40145267e3a5fcb259df69090a1e72 (diff)
downloadgitlab-ce-f01ca6dd804746e29d4a9cfdbfb4476870792de6.tar.gz
Add a note about persistent images for auto devops deployments
-rw-r--r--doc/topics/autodevops/index.md12
1 files changed, 12 insertions, 0 deletions
diff --git a/doc/topics/autodevops/index.md b/doc/topics/autodevops/index.md
index 5f5ba2b69bc..ec091549c05 100644
--- a/doc/topics/autodevops/index.md
+++ b/doc/topics/autodevops/index.md
@@ -309,6 +309,18 @@ enable them.
You can make use of [environment variables](#helm-chart-variables) to automatically
scale your pod replicas.
+It's important to note that when a project is deployed to a Kubernetes cluster,
+it relies on a Docker image that has been pushed to the
+[GitLab Container Registry](../../user/project/container_registry.md). Kubernetes
+fetches this image and uses it to run the application. If the project is public,
+the image can be accessed by Kubernetes without any authentication, allowing us
+to have deployments more usable. If the project is private/internal, the
+Registry requires credentials to pull the image. Currently, this is addressed
+by providing `CI_JOB_TOKEN` as the password that can be used, but this token will
+no longer be valid as soon as the deployment job finishes. This means that
+Kubernetes can run the application, but in case it should be restarted or
+executed somewhere else, it cannot be accessed again.
+
### Auto Monitoring
NOTE: **Note:**