summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorJoshua Lambert <joshua@gitlab.com>2017-08-22 14:13:43 -0400
committerJoshua Lambert <joshua@gitlab.com>2017-08-22 14:13:43 -0400
commitab7b54e0c7a5b7e00029601f3e74f5d23e114748 (patch)
tree29a43d4442b098c6c37614144fb79b6a4ac5e60d
parent16e0d6e76a0597331c8faf207ed4389f9d554066 (diff)
downloadgitlab-ce-ab7b54e0c7a5b7e00029601f3e74f5d23e114748.tar.gz
Fix spacing with code block36779-update-kubernetes-install-docs
-rw-r--r--doc/install/kubernetes/gitlab_chart.md1
-rw-r--r--doc/install/kubernetes/gitlab_omnibus.md3
-rw-r--r--doc/install/kubernetes/gitlab_runner_chart.md1
3 files changed, 5 insertions, 0 deletions
diff --git a/doc/install/kubernetes/gitlab_chart.md b/doc/install/kubernetes/gitlab_chart.md
index ae7c00aa928..81057736e3a 100644
--- a/doc/install/kubernetes/gitlab_chart.md
+++ b/doc/install/kubernetes/gitlab_chart.md
@@ -429,6 +429,7 @@ ingress:
> You may see a temporary error message `SchedulerPredicates failed due to PersistentVolumeClaim is not bound` while storage provisions. Once the storage provisions, the pods will automatically restart. This may take a couple minutes depending on your cloud provider. If the error persists, please review the [prerequisites](#prerequisites) to ensure you have enough RAM, CPU, and storage.
Ensure the GitLab repo has been added and re-initialize Helm:
+
```bash
helm repo add gitlab https://charts.gitlab.io
helm init
diff --git a/doc/install/kubernetes/gitlab_omnibus.md b/doc/install/kubernetes/gitlab_omnibus.md
index 01f0372fde3..05e0a59ffeb 100644
--- a/doc/install/kubernetes/gitlab_omnibus.md
+++ b/doc/install/kubernetes/gitlab_omnibus.md
@@ -127,6 +127,7 @@ Let's Encrypt limits a single TLD to five certificate requests within a single w
> You may see a temporary error message `SchedulerPredicates failed due to PersistentVolumeClaim is not bound` while storage provisions. Once the storage provisions, the pods will automatically restart. This may take a couple minutes depending on your cloud provider. If the error persists, please review the [prerequisites](#prerequisites) to ensure you have enough RAM, CPU, and storage.
Ensure the GitLab repo has been added and re-initialize Helm:
+
```bash
helm repo add gitlab https://charts.gitlab.io
helm init
@@ -135,11 +136,13 @@ helm init
Once you have reviewed the [configuration settings](#configuring-and-installing-gitlab) you can install the chart. We recommending saving your configuration options in a `values.yaml` file for easier upgrades in the future.
For example:
+
```bash
helm install --name gitlab -f values.yaml gitlab/gitlab-omnibus
```
or passing them on the command line:
+
```bash
helm install --name gitlab --set baseDomain=gitlab.io,baseIP=1.1.1.1,gitlab=ee,gitlabEELicense=$LICENSE,legoEmail=email@gitlab.com gitlab/gitlab-omnibus
```
diff --git a/doc/install/kubernetes/gitlab_runner_chart.md b/doc/install/kubernetes/gitlab_runner_chart.md
index 98f9fae9dc1..51f94a33109 100644
--- a/doc/install/kubernetes/gitlab_runner_chart.md
+++ b/doc/install/kubernetes/gitlab_runner_chart.md
@@ -191,6 +191,7 @@ certsSecretName: <SECRET NAME>
## Installing GitLab Runner using the Helm Chart
Ensure the GitLab repo has been added and re-initialize Helm:
+
```bash
helm repo add gitlab https://charts.gitlab.io
helm init