Skip to content

Yandex Cloud Integration

Available in GitFlic Enterprise edition

This integration enables GitFlic CI/CD pipelines to run on dedicated Yandex Cloud VMs with minimal computational resource downtime.

Yandex Cloud Configuration

1. Cloud Environment Setup

  • Review Yandex Cloud resource hierarchy
  • Check applicable quotas:
  • Default: 15 concurrent VM operations per folder
  • Default: 10 VMs maximum per cloud

2. Required Entities

  • Use default resources or create new:
  • 1 folder
  • 3 subnets
  • 1 security group
  • Create a service account with editor role

3. Authentication

4. VM Image

  • Obtain GitFlic's official cloud agent image

    Image access mechanics are currently in development

GitFlic Enterprise Configuration

1. Enable Features

Add to application.properties:

togglz.features.GITFLIC_YANDEX_RUNNER.enabled=true  
gitflic.ci-cd.cloud.enabled=true
Restart the application.

2. Agent Configuration

Navigate to Admin Panel → Settings → Yandex Agent Configurations

Configuration selection logic:
- Tasks with single tag → Matching config name
- Untagged tasks → Default config

Edit the default light configuration:
- Set VM image ID
- Specify subnet ID
- Configure security group

GitFlic Coordinator Setup

Required Properties

# Coordinator access  
gitflic.coordinator.url=  
gitflic.transport.url=  

# Cloud features  
togglz.features.GITFLIC_YANDEX_RUNNER.enabled=true  
gitflic.ci-cd.cloud.enabled=true  
togglz.features.GITFLIC_COMPANY_TARIFICATION.enabled=false  

# Yandex connection  
yandex.cloud.connection.service-account-id=  
yandex.cloud.connection.oauth-token=  
yandex.cloud.cloud-id=  

# Folder configuration  
yandex.cloud.folder-list[0].id=  
yandex.cloud.folder-list[0].operation-quota=15

Successful validation shows:
"Cloud CI/CD will start in X seconds"

Company-Level Activation

  1. Go to Admin Panel → Companies → Target Company → CI/CD Agent Management
  2. Enable:
  3. Allow cloud agents
  4. Set Maximum cloud agents

Advanced Configurations

Custom VM Image

  1. Launch VM from base image with metadata:
    maintenance-mode: 1
  2. Modify configuration
  3. Create new image
  4. Update image ID in admin panel

Private Docker Registry

Configure via CI/CD variables at:
- Service level
- Company level
- Project level
- Pipeline config 

YANDEX_DOCKER_REGISTRY_URL=  
YANDEX_DOCKER_REGISTRY_USER=  
YANDEX_DOCKER_REGISTRY_PASSWORD=  # (mask this variable)

Hot-Reserve Mode

# Enable hot-reserve  
gitflic.ci-cd.yandex.tactic.hot-reserve=false  

# Cloud agents process tasks unclaimed for N seconds (default: 300)  
gitflic.ci-cd.yandex.tactic.hot-reserve.agent.timeout=300

Automatic translation!

This page has been automatically translated. The text may contain inaccuracies