Installing GitLab Runner

GitLab Runner is an open-source application that runs GitLab CI/CD jobs in a pipeline using instructions from a special file named .gitlab-ci.yml. It helps run automated builds in a Managed Service for Kubernetes cluster.

Getting startedGetting started

1. Make sure that the security groups for the Managed Service for Kubernetes cluster and its node groups are configured correctly. If any rule is missing, add it.

   Warning

   The configuration of security groups determines the performance and availability of the cluster and the services and applications running in it.

2. Open the GitLab administration panel in your browser:

   • If GitLab is deployed on a Yandex Compute Cloud VM instance, use its public IP.
   • If GitLab is deployed in Yandex Managed Service for GitLab, use the instance FQDN.

3. Get the GitLab Runner authentication token (Runner authentication token):

   • To configure GitLab Runner throughout the GitLab instance (GitLab administrator access required):
     1. Click Admin area and select CI/CD → Runners.
     2. Click New instance runner and create a new GitLab Runner.
     3. Save the value of the Runner authentication token parameter.
   • To configure GitLab Runner for a group or project:
     1. Select a group or project you want to configure.
     2. On the left-hand side of the window that opens, click Settings and select the CI/CD option.
     3. Under Runners, click Expand.
     4. Click New project runner and create a new GitLab Runner.
     5. Save the value of the Runner authentication token parameter.

Installation using Yandex Cloud MarketplaceInstallation using Yandex Cloud Marketplace

1. Go to the folder page and select Managed Service for Kubernetes.
2. Click the name of the Managed Service for Kubernetes cluster you need and select the Marketplace tab.
3. Under Application available for installation, select GitLab Runner and click Go to install.
4. Configure the application:

   • Namespace: Select or create a namespace for GitLab Runner.

   • Application name: Specify the app name.

   • GitLab domain name: Enter a domain for your GitLab instance.

   • Registration token: Specify the token you obtained previously.

   • (Optional) Privileged mode for running docker:dind: Enable this option if you want to use docker:dind images.

     Warning

     The privileged mode increases the risk of information security incidents. Make sure to read the relevant documentation before using it.

   • (Optional) List of comma-separated tags: Provide a list of tags to distribute tasks between multiple GitLab Runners.

5. Click Install.
6. Wait for the application to change its status to Deployed.
7. Go back to the Runners page of your GitLab instance, reload the page, and make sure you see a new GitLab Runner.

Installation using a Helm chartInstallation using a Helm chart

1. Install Helm v3.8.0 or higher.

2. Install kubectl and configure it to work with the created cluster.

3. To install a Helm chart with GitLab Runner, run the following command:

   helm pull oci://cr.yandex/yc-marketplace/yandex-cloud/gitlab-org/gitlab-runner/chart/gitlab-runner \
     --version 0.54.0-8 \
     --untar && \
   helm install \
     --namespace <namespace> \
     --create-namespace \
     --set gitlabDomain=<VM_public_IP_address_or_GitLab_instance_FQDN> \
     --set runnerRegistrationToken=<previously_obtained_token> \
     gitlab-runner ./gitlab-runner/
   

   Note

   If you are using a Helm version below 3.8.0, append the export HELM_EXPERIMENTAL_OCI=1 && \ string to the command to enable Open Container Initiative (OCI) support in the Helm client.

Use casesUse cases

• Continuous deployment of containerized applications using GitLab.
• Scanning Container Registry for vulnerabilities during continuous deployment of applications using GitLab.
• Storing Docker images in Yandex Container Registry.

See alsoSee also

• Managed Service for GitLab documentation
• GitLab documentation
• Documentation for GitLab CI/CD
• Reference guide on .gitlab-ci.yml