Commit 5e353714 authored by DJ Mountney's avatar DJ Mountney

Merge branch 'jl-update-minikube-docs' into 'master'

Improve Minikube docs, including example instructions

See merge request charts/gitlab!782
parents 7f65ce1d 98279893
Pipeline #60057021 failed with stages
in 34 minutes and 39 seconds
......@@ -163,11 +163,33 @@ certificates will be generated. The `gitlab-runner` chart is not compatible with
self-signed certificates at this time, and as such, should be disabled by setting
`gitlab-runner.install=false`.
When using the recommended 3 CPU, 8 GB, use
### Deploying GitLab with recommended settings
When using the recommended 3 CPU and 8 GB of RAM, use
[`values-minikube.yaml`](https://gitlab.com/charts/gitlab/blob/master/examples/values-minikube.yaml)
as a base. If using _absolute minimum_ resources, you must reduce all replicas
as a base.
```shell
helm repo add gitlab https://charts.gitlab.io/
helm repo update
helm upgrade --install gitlab gitlab/gitlab \
--timeout 600 \
-f https://gitlab.com/charts/gitlab/raw/master/examples/values-minikube.yaml
```
### Deploying GitLab with minimal settings
If using _absolute minimum_ resources, 2 CPU and 4GB of RAM, you must reduce all replicas
and disable unneeded services. See [`values-minikube-minimum.yaml`](https://gitlab.com/charts/gitlab/blob/master/examples/values-minikube-minimum.yaml)
as reasonable base.
as a reasonable base.
```shell
helm repo add gitlab https://charts.gitlab.io/
helm repo update
helm upgrade --install gitlab gitlab/gitlab \
--timeout 600 \
-f https://gitlab.com/charts/gitlab/raw/master/examples/values-minikube-minimum.yaml
```
### Handling DNS
......@@ -196,3 +218,10 @@ depends on your operating system.
[BounCA](https://www.bounca.org) has a [good tutorial](https://www.bounca.org/tutorials/install_root_certificate.html),
covering most operating systems.
### Logging in
You can access the GitLab instance by visiting the domain specified, [https://gitlab.192.168.99.100.nip.io](https://gitlab.192.168.99.100.nip.io) is used in these examples. If you manually created the secret for initial root password, you can use that to sign in as root user. If not, Gitlab automatically created a random password for the root user. This can be extracted by the following command (replace <name> by name of the release - which is gitlab if you used the command above).
```shell
kubectl get secret <name>-gitlab-initial-root-password -ojsonpath='{.data.password}' | base64 --decode ; echo
```
\ No newline at end of file
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment