App service
Services/GitLab Runner

GitLab Runner service

GitLab Runner service for executing jobs from a linked GitLab installation in separate Kubernetes pods.

Use it as a reusable, versioned service inside custom or predefined stacks so teams can keep the runtime and operational model consistent.

All services

Why teams use this service

Technical profile

Review versions, ports, source, and packaging.

Stacks that use it

See where this service fits in ready-made stacks.

Runtime wiring and defaults

See ports, links, storage, configs, and runtime behavior.

Overview

Technical profile and packaging

This page shows how GitLab Runner is packaged and versioned as a Wodby service, what it exposes at runtime, and which source artifacts it builds on.

Service type

App service

Versions

19

Labels

gitlab-runner, ci, runner

Stacks

Use it inside ready-made stacks or your own

These public stacks already include GitLab Runner as part of their default service model. You can start there and customize the stack, or compose your own stack around the same building block.
GitLab

Runtime wiring

Reuse connectivity, storage, and runtime defaults

This service can expose ports, connect to other services, attach persistent storage, and define runtime defaults that become reusable inside stacks rather than being rebuilt case by case.

Settings

1 setting can be overridden per environment.

Service links

These links define which other services can connect to GitLab Runner when it is used inside a stack.