| ... | ... | @@ -6,6 +6,9 @@ This is a document made to help with configuring GitLab autodevops. This documen |
|
|
|
|
|
|
|
* [Google OAuth2](#google-oauth2)
|
|
|
|
* [Creating a Kubernetes cluster from within GitLab](#creating-a-kubernetes-cluster-from-within-gitLab)
|
|
|
|
* [SSL settings](#ssl-settings)
|
|
|
|
* [Enabling Autodevops](#enabling-autodevops)
|
|
|
|
* [Container Registry domain configuration](#container-registry-domain-configuration)
|
|
|
|
|
|
|
|
|
|
|
|
## Google OAuth2
|
| ... | ... | @@ -56,3 +59,17 @@ docker exec -it gitlab bash -c 'gitlab-ctl restart' |
|
|
|
|
|
|
|
Also it seems like that if you are trying to install Helm Tiller too fast after cluster is build you may face following error and you need to just wait couple of minutes, refresh and try installing again:
|
|
|
|
|
|
|
|
|
|
|
|
## SSL settings
|
|
|
|
You can automatically fetch certificate for GitLab omnibus by following official guide [here](https://docs.gitlab.com/omnibus/settings/ssl.html).
|
|
|
|
|
|
|
|
## Container Registry domain configuration
|
|
|
|
To configure Container Registry follow official guide [here](https://gitlab.labranet.jamk.fi/help/administration/container_registry.md#container-registry-domain-configuration).
|
|
|
|
|
|
|
|
:exclamation: **Note** that you need to have certificate for GitLab for Container Rergistry to work. [SSL settings](#ssl-settings)
|
|
|
|
|
|
|
|
## Enabling autodevops
|
|
|
|
To enable autodevops for GitLab follow the official guide [here](https://docs.gitlab.com/ee/topics/autodevops/quick_start_guide.html#enabling-auto-devops).
|
|
|
|
|
|
|
|
:exclamation: **Note** that you need to enable Registry for GitLab
|
|
|
|
|
