kotovalexarian-likes-gitlab
/
gitlab-org--gitlab-foss
1
0
Fork 0
Code Releases Activity

Make k8s trade-offs less intimidating

This commit is contained in:
Achilleas Pipinellis 2018-12-04 09:24:09 +01:00
parent 81869d22d9
commit a2accebb80
No known key found for this signature in database
GPG Key ID: A0996FBD3E92C17B
1 changed files with 3 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
doc/install/README.md
View File

@ -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