Role
Disabled by default
GitLab Runner in the GitLab stack
This page explains what GitLab Runner means in the GitLab stack: how it is included, which base service it uses, and how it connects to the rest of the stack.
GitLab Runner is available in the GitLab stack but starts disabled, so teams can turn it on only when a specific app needs it.
Base service
GitLab Runner
Type
service
Delivery
Prebuilt service image
Stack fit
How GitLab Runner fits into this stack
GitLab Runner is available in the GitLab stack but starts disabled, so teams can turn it on only when a specific app needs it.
This stack service is based on GitLab Runner and keeps the service-specific setup for GitLab in one place.
It is linked to GitLab Community Edition inside the stack.
Version policy
Available versions include 19.
Inclusion
Enabled by default: No
Required: No
Primary: No
Connections
gitlab: GitLab Community Edition
Storage
This stack service does not define persistent volume sizes.
Stack-specific technical details
Review the operational capabilities exposed by GitLab Runner inside this stack, including backups, imports, configs, settings, cron, actions, storage, and service links where they exist.
Settings
Tune service behavior per environment while keeping one reusable stack baseline.
Runner authentication token
Service links
See how services are wired together so dependencies stay consistent across environments.
GitLab
Linked to GitLab Community Edition. Required.