GitLab

Last update: October 05 2026Open in Markdown

GitLab is an open-source platform for storing project repositories and automating CI/CD using built-in pipelines and an error tracking system. GitLab supports the full CI/CD cycle — continuous integration, building, testing, and code deployment.

You can create a cloud server with a pre-installed GitLab application. In Russia, the application runs on a cloud server with the configured SelectOS 1 64-bit operating system. In other countries — Ubuntu 22.04.

Before creating a cloud server with the application, review the software license agreements included in the image.

Minimum resource requirements

	Up to 500 users	From 500 users
vCPU count	4	8
RAM	8 GB	16 GB
Boot volume	20 GB	40 GB

Create a cloud server with GitLab

For your information

The cloud server with GitLab will be accessible via SSH on port 22022.

For GitLab to work, the cloud server must be accessible from the internet. To do this, when creating the server, you must create a private subnet and connect a public floating IP address. To configure GitLab, you must specify the application parameters when creating the server. In the parameters, you can configure GitLab:

• with automatic creation of a PostgreSQL database on the server;
• with connecting the created PostgreSQL Cloud Database.

After creating a server with GitLab, a free Let’s Encrypt® TLS certificate will be automatically issued for the domain you specify. To issue a certificate, you need to add an A record for the domain and specify the server's public floating IP address in the record value. You can add the domain to Selectel DNS hosting (actual).

1. Create a public floating IP address.

2. Add an A record for the domain.

3. Create a cloud server with GitLab.

1. Create a public floating IP address

Create a public floating IP address so that the GitLab cloud server is accessible from the internet.

Use the Create a public floating IP address subsection of the Public floating IP addresses instructions.

2. Add an A record for the domain⁠

Add a resource record to access GitLab by domain.

Specify:

• resource record type in the group — A;
• record value — public floating IP address that you created in step 1.

3. Create a cloud server with GitLab

1. In the control panel, in the top menu, click Products and select Cloud Servers.

2. Click Create Server.

3. Fill in the blocks:

   • Name and location;
   • Source;
   • Configuration;
   • Disks;
   • Internet;
   • Private network;
   • Security;
   • Access;
   • Additional settings.

4. Check the cloud server price.

5. Click Create.

Name and location

1. Enter the server name. It will be set as the hostname in the operating system.

2. Select the location where the server will be created. The list of available server configurations and resource cost depend on the location. You cannot change the location after creating the server.

Source

1. Open the Applications tab.

2. Select Cloud GitLab.

3. Optional: if you need a different current or archived application version, in the Version field, select the desired version.

4. Fill in the application parameters:

   4.1. In the GitLab domain field, enter the domain for accessing GitLab that you added in step 2.

   4.2. Enter the GitLab administrator's email address. This email will be used to issue SSL certificates.

   4.3. Enter the administrator password for logging into GitLab.

   4.4. Enter the PostgreSQL database username. If you will use an external database, enter the username for this DB. You can view the username in the Control panel: in the top menu, click Products → Managed Databases → cluster page → Databases tab → database card → Database owner field.

   4.5. Enter the PostgreSQL database user password. If you will use an external database, enter the user password for this DB. The password is not stored in the control panel — if you lost it, change the password.

   4.6. Optional: if you need to use a different email for the Let's Encrypt® certificate, open the Additional application parameters block and enter it in the Email for Let's Encrypt field.

   4.7. Optional: enable an existing database by opening the Additional application parameters block and selecting the Use external database (DBaaS) checkbox. In the External database host field, specify the DNS address of the PostgreSQL cloud DB. You can view the DNS address in the Control panel: in the top menu, click Products → Managed Databases → cluster page → Settings tab → Node addresses and statuses block → DNS addresses tab.

   4.8. Optional: specify the SSL certificate verification mode by opening the Additional application parameters block and entering a value in the External database SSL mode field.

   4.9. Optional: specify the external database port by opening the Additional application parameters block and entering the port in the External database port field. The default port is 5432.

Configuration

Select a configuration from 4 vCPUs, RAM from 8 GB, and boot disk size from 20 GB for 500 GitLab users and fewer. For all lines except Shared and Dedicated, two types of server configurations are available:

• fixed configurations — configurations of lines with different technical specifications, in which the ratio of resources is fixed;
• custom configurations — configurations in which you can specify any ratio of resources.

Configurations use different processors depending on the line and pool segment. You can customize the selected configuration. After creating the server, you will be able to change the configuration.

Fixed configuration

1. Open the tab with the line.

2. Click Fixed.

3. Optional: you can customize the configuration if you are creating a server in the ru-6 multi-AZ pool segment or pool segments ru-3b, ru-7a, and ru-7b:

   3.1. Expand the block with the configuration settings description.

   3.2. Optional: select a processor manufacturer. Selecting a manufacturer is not available in all pools.

   3.3. Optional: if you do not want physical processor cores to be assigned to the cloud server vCPUs, uncheck the Dedicated cores checkbox. For more information, see the Dedicated Cores instructions.

   3.4. Optional: if you want to disable Hyper-Threading for a server with dedicated cores, uncheck the Hyper-Threading (SMT) checkbox.

   3.5. Optional: if you are creating a server with dedicated cores and want to place a multi-processor server on a single NUMA node, check the Mandatory placement on a single NUMA node checkbox. A server with 4 vCPUs or more can be placed on a single NUMA node. If the cloud server resources cannot be placed on a single node, it will not be created. For more information, see the Placement on a Single NUMA Node section of the Dedicated Cores instructions.

4. Select a configuration.

5. If both local and network disks are available in the selected configuration, select the disk to be used as the boot disk:

   • local disk — check the Local SSD NVMe disk checkbox. A server with a local disk can only be created from images and applications;
   • network disk — do not check the Local SSD NVMe disk checkbox.

   The amount of RAM allocated to the server may be less than specified in the configuration — the operating system kernel reserves part of the RAM depending on the kernel version and distribution. You can check the allocated amount on the server using the sudo dmesg | grep Memory command.

Custom configuration

1. Open the tab with the line.

2. Click Custom.

3. Optional: you can customize the configuration if you are creating a server in the ru-6 multi-AZ pool segment or pool segments ru-3b, ru-7a, and ru-7b:

   3.1. Expand the block with the configuration settings description.

   3.2. Optional: select a processor manufacturer. Selecting a manufacturer is not available in all pools.

   3.3. Optional: if you do not want physical processor cores to be assigned to the cloud server vCPUs, uncheck the Dedicated cores checkbox. For more information, see the Dedicated Cores instructions.

   3.4. Optional: if you want to disable Hyper-Threading for a cloud server with dedicated cores, uncheck the Hyper-Threading (SMT) checkbox.

   3.5. Optional: if you are creating a cloud server with dedicated cores and want to place a multi-processor server on a single NUMA node, check the Mandatory placement on a single NUMA node checkbox. A cloud server with 4 vCPUs or more can be placed on a single NUMA node. If the cloud server resources cannot be placed on a single node, it will not be created. For more information, see the Placement on a Single NUMA Node section of the Dedicated Cores instructions.

4. Specify the number of vCPUs.

5. Specify the RAM size.

6. If you need to add graphics processing units to the server, click Add GPU, select the GPU type, and specify the number of GPUs. The selected line will change to the GPU line. If you selected an image without GPU optimization in the Source block and the Auto-select GPU image toggle switch is enabled, the selected image will automatically switch to a GPU-optimized image.

7. If both local and network disks are available in the selected configuration, select the disk to be used as the boot disk:

   • local disk — check the Local SSD NVMe disk checkbox. A server with a local disk can only be created from images and applications;
   • network disk — do not check the Local SSD NVMe disk checkbox.

   The amount of RAM allocated to the server may be less than specified in the configuration — the operating system kernel reserves part of the RAM depending on the kernel version and distribution. You can check the allocated amount on the server using the sudo dmesg | grep Memory command.

Disks

1. If you did not check the Local SSD NVMe disk checkbox when customizing the configuration, the first specified network disk will be used as the server boot disk. To configure it:

   1.1. Select the boot network disk type.

   1.2. Specify the network boot disk size in GB or TB. Take into account the network disk limits on maximum size.

   1.3. If you selected the Universal v2 or Fast SSD v2 disk type, specify the total number of read and write operations in IOPS. After creating the disk, you can change the number of IOPS — decrease or increase it. The number of IOPS changes is unlimited.

2. Add an additional network disk of the server . An additional disk is required to launch GitLab and is used to store primary data, such as databases or repositories.:

   2.1. Click Add.

   2.2. Select the network disk type.

   2.3. Specify a network disk size from 30 GB. Take into account the network disk limits on maximum size.

   2.4. If you selected the Universal v2 or Fast SSD v2 disk type, specify the total number of read and write operations in IOPS. After creating the disk, you can change the number of IOPS — decrease or increase it. The number of IOPS changes is unlimited.

   After creating the server, you will be able to attach new additional disks.

Internet

Configure public access to the server.

The cloud server will be added to the private subnet connected to the cloud router with 1:1 NAT and internet access. Internet access to and from the internet will be carried out via the cloud router. The server will be accessible from the internet via a public floating IP address.

1. In the Connecting from the internet field, select the Public floating IP address access type.

2. Select the public floating IP address you created in Step 1.

Private network

A cloud server can be added to an existing or new private subnet.

Existing private subnet

1. In the Subnet field, select a private subnet.

2. Optional: in the IP address field, change the default IP address.

3. In the Router field, select an existing router or create a new one.

   If the router is not connected to the internet, it will be automatically connected to the internet after the server is created.

New private subnet

1. In the Subnet field, select New private subnet.

2. In the Network field, select an existing network or create a new one.

3. Optional: change the subnet CIDR.

4. Optional: in the IP address field, change the default IP address.

5. In the Router field, select an existing router or create a new one.

   If the router is not connected to the internet, it will be automatically connected to the internet after the server is created.

Security

Select security groups to filter traffic on server ports. Without security groups, traffic will be blocked. If the block is missing, traffic filtering (port security) is disabled in the server network. With traffic filtering disabled, all traffic will be allowed.

Access

1. Place a project SSH key on the server for secure connection:

   1.1. If the project SSH key has not been added to the cloud platform, click Add SSH key, enter the key name, paste the public key in OpenSSH format, and click Add.

   1.2. If the project SSH key has been added to the cloud platform, in the SSH key field, select the existing key. The SSH key is only available in the pool where it is placed.

2. Optional: in the Password for "root" field:

   2.1. Copy the password of the root user — a user with unrestricted permissions for all actions on the system.

   2.2. Save the password in a safe place and do not share it in plain text.

Additional settings

1. Optional: if you plan to create multiple servers and want to increase infrastructure fault tolerance, add the server to a placement group:

   1.1. To create a new group, in the Placement group field, click Create.

   1.2. Select New group and enter the group name.

   1.3. Select a placement policy on different hosts:

   • desirable — soft-anti-affinity. The system will try to place the servers on different hosts. If there is no suitable host when creating the server, it will be created on the same host;
   • mandatory — anti-affinity. Servers in the group must be located on different hosts. If there is no suitable host when creating the server, the server will not be created.

   1.4. If the group has been created, in the Placement group field, select the placement group.

2. Optional: to add additional information or filter servers in the list, add server tags. Operating system and configuration tags are added automatically. To add a new tag, in the Tags field, enter the tag.

3. To add a script that will be executed using the cloud-init agent on the first boot of the operating system, in the Automation block, in the User data field:

   • open the Text tab and paste the script as text;
   • or open the File tab and upload the file with the script.