Yandex Cloud
Search
Contact UsTry it for free
  • Customer Stories
  • Documentation
  • Blog
  • All Services
  • System Status
    • Featured
    • Infrastructure & Network
    • Data Platform
    • Containers
    • Developer tools
    • Serverless
    • Security
    • Monitoring & Resources
    • AI for business
    • Business tools
  • All Solutions
    • By industry
    • By use case
    • Economics and Pricing
    • Security
    • Technical Support
    • Start testing with double trial credits
    • Cloud credits to scale your IT product
    • Gateway to Russia
    • Cloud for Startups
    • Center for Technologies and Society
    • Yandex Cloud Partner program
    • Price calculator
    • Pricing plans
  • Customer Stories
  • Documentation
  • Blog
© 2025 Direct Cursus Technology L.L.C.
Yandex Managed Service for GitLab
  • Getting started
    • Service resource interdependencies
    • Advantages over a custom GitLab installation
    • Running migration from a custom GitLab installation
    • Approval rules
    • Backups
    • Security in GitLab
    • Quotas and limits
  • Access management
  • Pricing policy
  • Terraform reference
  • Monitoring metrics
  • Audit Trails events
  • Release notes
  • FAQ

In this article:

  • GitLab instance
  • Instance configuration
  • GitLab Runner
  • GitLab Pages
  • Use cases
  1. Concepts
  2. Service resource interdependencies

Resource relationships in Managed Service for GitLab

Written by
Yandex Cloud
Updated at July 22, 2025
  • GitLab instance
  • Instance configuration
  • GitLab Runner
  • GitLab Pages
  • Use cases

GitLab is an open-source web-based DevOps lifecycle tool. It is a code repository management system for Git with error tracking, CI/CD pipeline, dedicated Wiki, and other features.

Managed Service for GitLab helps configure application deployment on VMs in Yandex Compute Cloud and supports integration with Yandex Container Registry and Yandex Managed Service for Kubernetes.

How Managed Service for GitLab works:

GitLab instanceGitLab instance

A GitLab instance is the service's primary entity. It is a VM deployed in Yandex Cloud. Managed Service for GitLab takes care of its routine maintenance, such as storage fault tolerance, security updates, automated GitLab version upgrades, and so on.

Users can mange instances from the Yandex Cloud management console, CLI, and API.

Instance configurationInstance configuration

When creating an instance, you specify:

  • Instance type: The number of vCPUs and the amount of RAM. Available instance types:

    Type Computing resources
    s2.micro 2 vCPUs, 8 GB RAM
    s2.small 4 vCPUs, 16 GB RAM
    s2.medium 8 vCPUs, 32 GB RAM
    s2.large 16 vCPUs, 64 GB RAM

    After you create an instance, you can change its type to a higher performing one.

  • Subnet.

    Warning

    For the time being, Yandex Cloud technical restrictions do not allow selecting a subnet with an address range of 192.168.0.0/24.

  • Disk size. After you create an instance, you can increase its disk size.

  • Name in the .gitlab.yandexcloud.net domain: Your GitLab instance's internet address.

  • Administrator information:

    • Email.
    • Login.

Note

When you create an instance in Managed Service for GitLab, it automatically generates an SSL certificate. No additional configuration for using HTTPS is required.

GitLab RunnerGitLab Runner

GitLab Runner is an open-source application which executes GitLab CI/CD pipeline jobs based on instructions from a special file named .gitlab-ci.yml. It helps run automated builds in Managed Service for Kubernetes clusters and on Compute Cloud VMs.

You can get started with GitLab Runner in the following ways:

  • Install GitLab Runner in a Managed Service for Kubernetes cluster.

  • Create a Compute Cloud VM and install GitLab Runner on it manually.

  • Use the management console to create a runner that will automatically deploy the specified number of Compute Cloud VMs.

    When creating a runner from the management console, you can select the following 15 to 500 GB disk types for the VM storage:

    • HDD
    • SSD

    The following computing resource configurations are available:

    • 2 vCPUs, 4 GB RAM
    • 2 vCPUs, 8 GB RAM
    • 4 vCPUs, 16 GB RAM
    • 8 vCPUs, 64 GB RAM
    • 16 vCPUs, 128 GB RAM

    Note

    The feature of creating and managing runners using the management console is at the Preview stage. To request access, contact support or your account manager.

GitLab PagesGitLab Pages

GitLab Pages is a tool for publishing static websites composed of files residing in a GitLab repository. Websites are deployed by GitLab CI/CD jobs. GitLab Pages works with static website generators and standard HTML, CSS, and JavaScript files.

GitLab Pages enables you to use your own domains and SSL/TLS certificates and to configure access to websites.

For more information, see the official GitLab documentation.

Note

This feature is in the Preview stage. To get access, contact tech support or your account manager.

Use casesUse cases

  • Secure storage of GitLab CI passwords as Yandex Lockbox secrets
  • Building a CI/CD pipeline using serverless products
  • Deploying GitLab Runner on a Yandex Compute Cloud virtual machine
  • Continuous deployment of containerized Managed Service for Kubernetes applications

Was the article helpful?

Previous
Integration with Argo CD
Next
Advantages over a custom GitLab installation
© 2025 Direct Cursus Technology L.L.C.