summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorThong Kuah <tkuah@gitlab.com>2019-04-01 21:57:30 +0000
committerThong Kuah <tkuah@gitlab.com>2019-04-02 11:01:22 +1300
commit74b14199acbccba1bd219ed938e57022c6ee7420 (patch)
tree982dc3f7b58e7224141828588e06d3d6a4ab1886
parent16409a291733299aff1b6e6957b689726636f3d6 (diff)
downloadgitlab-ce-58879-document-local-tiller-docs.tar.gz
Apply suggestion to doc/topics/autodevops/index.md58879-document-local-tiller-docs
-rw-r--r--doc/topics/autodevops/index.md8
1 files changed, 4 insertions, 4 deletions
diff --git a/doc/topics/autodevops/index.md b/doc/topics/autodevops/index.md
index 89397364117..fd99b06b863 100644
--- a/doc/topics/autodevops/index.md
+++ b/doc/topics/autodevops/index.md
@@ -471,8 +471,8 @@ used. Previous versions of GitLab had a Tiller installed in the project
namespace.
CAUTION: **Caution:**
-Your apps should *not* be manipulated outside of Helm (using Kubernetes directly.)
-This can cause confusion with Helm not detecting the change, and subsequent
+Your apps should *not* be manipulated outside of Helm (using Kubernetes directly).
+This can cause confusion with Helm not detecting the change and subsequent
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.
@@ -539,8 +539,8 @@ used. Previous versions of GitLab had a Tiller installed in the project
namespace.
CAUTION: **Caution:**
-Your apps should *not* be manipulated outside of Helm (using Kubernetes directly.)
-This can cause confusion with Helm not detecting the change, and subsequent
+Your apps should *not* be manipulated outside of Helm (using Kubernetes directly).
+This can cause confusion with Helm not detecting the change and subsequent
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.