Resource relationships in Managed Service for GitLab
GitLab is an open-source web-based DevOps lifecycle tool. It is a system for managing code repositories for Git with error tracking, a CI/CD pipeline, a dedicated Wiki, and other functionality.
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 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 configuration
When creating an instance, you specify:
-
Instance type: The number of vCPUs and the amount of RAM. After creating an instance, you can change its type only by contacting support.
-
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. -
Storage size. After creating an instance, you can increase its storage space only by contacting support. It is not possible to reduce storage size.
-
Name in the
.gitlab.yandexcloud.netdomain: 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.