From ab7b54e0c7a5b7e00029601f3e74f5d23e114748 Mon Sep 17 00:00:00 2001 From: Joshua Lambert Date: Tue, 22 Aug 2017 14:13:43 -0400 Subject: [PATCH] Fix spacing with code block --- doc/install/kubernetes/gitlab_chart.md | 1 + doc/install/kubernetes/gitlab_omnibus.md | 3 +++ doc/install/kubernetes/gitlab_runner_chart.md | 1 + 3 files changed, 5 insertions(+) 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: ## 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