diff options
| author | Mayra Cabrera <mcabrera@gitlab.com> | 2018-03-06 08:56:01 -0600 |
|---|---|---|
| committer | Mayra Cabrera <mcabrera@gitlab.com> | 2018-03-06 08:56:01 -0600 |
| commit | d9271ed77dba41eb0cd5ac916ce4340dd81a04c8 (patch) | |
| tree | 74886938d5943d866f7139a5ab6700854ee88aa2 | |
| parent | d5c82e79a0d6c8bc1cb288b9c083fa1f80baa3dd (diff) | |
| download | gitlab-ce-43259-document-persistent-images-for-autodevops-deployments.tar.gz | |
Rephrase benefits and limitations of autodevops43259-document-persistent-images-for-autodevops-deployments
| -rw-r--r-- | doc/topics/autodevops/index.md | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/doc/topics/autodevops/index.md b/doc/topics/autodevops/index.md index 2267d8c69ac..129d604f7a8 100644 --- a/doc/topics/autodevops/index.md +++ b/doc/topics/autodevops/index.md @@ -297,9 +297,6 @@ deploys with Auto DevOps can undo your changes. Also, if you change something and want to undo it by deploying again, Helm may not detect that anything changed in the first place, and thus not realize that it needs to re-apply the old config. -CAUTION: **Caution:** -From 10.5 the Auto Deploy manages a direct access to [GitLab Container Registry](https://docs.gitlab.com/ce/user/project/container_registry.html) for public projects since the images are accessible with no authentication. This can cause a problem if, for some reason, the Kubernetes cluster needs to reload the image for private or internal projects as it will not have access to this images. - After a branch or merge request is merged into the project's default branch (usually `master`), Auto Deploy deploys the application to a `production` environment in the Kubernetes cluster, with a namespace based on the project name and unique @@ -312,6 +309,9 @@ 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](https://docs.gitlab.com/ce/user/project/container_registry.html). 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 is no longer 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:** |