Role
Required
Valkey in the GitLab stack
This page explains what Valkey means in the GitLab stack: how it is included, which base service it uses, and how it connects to the rest of the stack.
Valkey is included by default and treated as a required part of the GitLab stack.
Base service
Valkey
Type
datastore
Delivery
Prebuilt service image
Stack fit
How Valkey fits into this stack
Valkey is included by default and treated as a required part of the GitLab stack.
This stack service is based on Valkey and keeps the service-specific setup for GitLab in one place.
Version policy
This stack service is limited to 8.1.
Inclusion
Enabled by default: Yes
Required: Yes
Primary: No
Connections
No explicit service links are defined for this stack service.
Storage
data: 10 GB
Stack-specific technical details
Review the operational capabilities exposed by Valkey inside this stack, including backups, imports, configs, settings, cron, actions, storage, and service links where they exist.
Volumes
Provision the persistent storage and shared volume relationships the stack expects.
Data
Optional.