summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorAchilleas Pipinellis <axil@gitlab.com>2018-12-04 09:24:09 +0100
committerAchilleas Pipinellis <axil@gitlab.com>2018-12-04 09:24:09 +0100
commita2accebb80cea53b864ad3db4023656f9884fbf4 (patch)
treeec9ec0c8422145e0ca82e990c5753f8f73ccf17b
parent81869d22d9b8a26ec4eb9ebbea41688d1d7ede62 (diff)
downloadgitlab-ce-a2accebb80cea53b864ad3db4023656f9884fbf4.tar.gz
Make k8s trade-offs less intimidating
-rw-r--r--doc/install/README.md8
1 files changed, 3 insertions, 5 deletions
diff --git a/doc/install/README.md b/doc/install/README.md
index 8eca5d3f164..f1f9020747a 100644
--- a/doc/install/README.md
+++ b/doc/install/README.md
@@ -28,7 +28,7 @@ the hardware requirements.
## Install GitLab using the Omnibus GitLab package (recommended)
This installation method uses the Omnibus GitLab package, using our official
-deb/rpm repositories. This is the recommended way.
+deb/rpm repositories. This is recommended for most users.
If you need additional flexibility and resilience, we recommend deploying
GitLab as described in our [High Availability documentation](../administration/high_availability/README.md).
@@ -54,11 +54,9 @@ We recommend being familiar with Kubernetes before using it to deploy GitLab in
production. The methods for management, observability, and some concepts are
different than traditional deployments.
-When installing GitLab on kubernetes, there are a number of trade-offs that you
-need to be aware of that may not be immediately obvious and could prevent you
-getting the best experience from GitLab:
+When installing GitLab on Kubernetes, there are some trade-offs that you
+need to be aware of:
-- Configuration of features such as object storage and backups can be more challenging.
- Administration and troubleshooting requires Kubernetes knowledge.
- It can be more expensive for smaller installations. The default installation
requires more resources than a single node Omnibus deployment, as most services