Yandex Cloud
Search
Contact UsGet started
  • Blog
  • Pricing
  • Documentation
  • All Services
  • System Status
    • Featured
    • Infrastructure & Network
    • Data Platform
    • Containers
    • Developer tools
    • Serverless
    • Security
    • Monitoring & Resources
    • ML & AI
    • Business tools
  • All Solutions
    • By industry
    • By use case
    • Economics and Pricing
    • Security
    • Technical Support
    • Customer Stories
    • Cloud credits to scale your IT product
    • Gateway to Russia
    • Cloud for Startups
    • Education and Science
    • Yandex Cloud Partner program
  • Blog
  • Pricing
  • Documentation
© 2025 Direct Cursus Technology L.L.C.
Yandex Managed Service for GitLab
  • Getting started
    • Resource relationships
    • 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
  • Monitoring metrics
  • Audit Trails events
  • Release notes
  • FAQ

In this article:

  • GitLab instance
  • Instance configuration
  • Use cases
  1. Concepts
  2. Resource relationships

Resource relationships in Managed Service for GitLab

Written by
Yandex Cloud
Updated at April 10, 2025
  • GitLab instance
  • Instance configuration
  • 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 to Yandex Compute Cloud virtual machines 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.

Instance configurationInstance configuration

When creating an instance, you specify:

  • Instance type: The number of vCPUs and the amount of 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.

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.