GitLab Runner Helm Chart

Officially supported cloud providers are Google Container Service and Azure Container Service.

Officially supported schedulers are Kubernetes and Terraform.

The gitlab-runner Helm chart deploys a GitLab Runner instance into your Kubernetes cluster.

This chart configures the Runner to:

Run using the GitLab Runner Kubernetes executor
For each new job it receives from GitLab CI, it will provision a new pod within the specified namespace to run it.

Prerequisites

Your GitLab Server's API is reachable from the cluster
Kubernetes 1.4+ with Beta APIs enabled
The kubectl CLI installed locally and authenticated for the cluster
The Helm Client installed locally
The Helm Server (Tiller) already installed and running in the cluster, by running helm init
The GitLab Helm Repo added to your Helm Client. See Adding GitLab Helm Repo

Configuring GitLab Runner using the Helm Chart

Create a values.yaml file for your GitLab Runner configuration. See Helm docs for information on how your values file will override the defaults.

The default configuration can always be found in the values.yaml in the chart repository.

Required configuration

In order for GitLab Runner to function, your config file must specify the following:

gitlabURL - the GitLab Server URL (with protocol) to register the runner against
runnerRegistrationToken - The Registration Token for adding new Runners to the GitLab Server. This must be retrieved from your GitLab Instance. See the GitLab Runner Documentation for more information.

Other configuration

The rest of the configuration is documented in the values.yaml in the chart repository.

Here is a snippet of the important settings:

## The GitLab Server URL (with protocol) that want to register the runner against
## ref: https://docs.gitlab.com/runner/commands/README.html#gitlab-runner-register
##
gitlabURL: http://gitlab.your-domain.com/

## The Registration Token for adding new Runners to the GitLab Server. This must
## be retreived from your GitLab Instance.
## ref: https://docs.gitlab.com/ce/ci/runners/README.html#creating-and-registering-a-runner
##
runnerRegistrationToken: ""

## Configure the maximum number of concurrent jobs
## ref: https://docs.gitlab.com/runner/configuration/advanced-configuration.html#the-global-section
##
concurrent: 10

## Defines in seconds how often to check GitLab for a new builds
## ref: https://docs.gitlab.com/runner/configuration/advanced-configuration.html#the-global-section
##
checkInterval: 30

## Configuration for the Pods that that the runner launches for each new job
##
runners:
  ## Default container image to use for builds when none is specified
  ##
  image: ubuntu:16.04

  ## Run all containers with the privileged flag enabled
  ## This will allow the docker:dind image to run if you need to run Docker
  ## commands. Please read the docs before turning this on:
  ## ref: https://docs.gitlab.com/runner/executors/kubernetes.html#using-docker-dind
  ##
  privileged: false

  ## Namespace to run Kubernetes jobs in (defaults to 'default')
  ##
  # namespace:

  ## Build Container specific configuration
  ##
  builds:
    # cpuLimit: 200m
    # memoryLimit: 256Mi
    cpuRequests: 100m
    memoryRequests: 128Mi

  ## Service Container specific configuration
  ##
  services:
    # cpuLimit: 200m
    # memoryLimit: 256Mi
    cpuRequests: 100m
    memoryRequests: 128Mi

  ## Helper Container specific configuration
  ##
  helpers:
    # cpuLimit: 200m
    # memoryLimit: 256Mi
    cpuRequests: 100m
    memoryRequests: 128Mi

Running Docker-in-Docker containers with GitLab Runners

See Running Privileged Containers for the Runners for how to enable it, and the GitLab CI Runner documentation on running dind.

Running privileged containers for the Runners

You can tell the GitLab Runner to run using privileged containers. You may need this enabled if you need to use the Docker executable within your GitLab CI jobs.

This comes with several risks that you can read about in the GitLab CI Runner documentation.

If you are okay with the risks, and your GitLab CI Runner instance is registered against a specific project in GitLab that you trust the CI jobs of, you can enable privileged mode in values.yaml:

runners:
  ## Run all containers with the privileged flag enabled
  ## This will allow the docker:dind image to run if you need to run Docker
  ## commands. Please read the docs before turning this on:
  ## ref: https://docs.gitlab.com/runner/executors/kubernetes.html#using-docker-dind
  ##
  privileged: true

Installing GitLab Runner using the Helm Chart

Once you have configured GitLab Runner in your values.yml file, run the following:

helm install --namespace <NAMESPACE> --name gitlab-runner -f <CONFIG_VALUES_FILE> gitlab/gitlab-runner

<NAMESPACE> is the Kubernetes namespace where you want to install the GitLab Runner.
<CONFIG_VALUES_FILE> is the path to values file containing your custom configuration. See the Configuration section to create it.

Updating GitLab Runner using the Helm Chart

Once your GitLab Runner Chart is installed, configuration changes and chart updates should we done using helm upgrade

helm upgrade --namespace <NAMESPACE> -f <CONFIG_VALUES_FILE> <RELEASE-NAME> gitlab/gitlab-runner

Where:

<NAMESPACE> is the Kubernetes namespace where GitLab Runner is installed
<CONFIG_VALUES_FILE> is the path to values file containing your custom configuration. See the Configuration section to create it.
<RELEASE-NAME> is the name you gave the chart when installing it. In the Install section we called it gitlab-runner.

Uninstalling GitLab Runner using the Helm Chart

To uninstall the GitLab Runner Chart, run the following:

helm delete --namespace <NAMESPACE> <RELEASE-NAME>

where:

<NAMESPACE> is the Kubernetes namespace where GitLab Runner is installed
<RELEASE-NAME> is the name you gave the chart when installing it. In the Install section we called it gitlab-runner.

6.8 KiB Raw Blame History