Role
Enabled by default
Valkey in the WordPress stack
This page explains what Valkey means in the WordPress stack: how it is included, which base service it uses, and how it connects to the rest of the stack.
Valkey is enabled by default in instances created from the WordPress stack, but it is not treated as a core required service.
Base service
Valkey
Type
datastore
Stack fit
How Valkey fits into this stack
Valkey is enabled by default in instances created from the WordPress stack, but it is not treated as a core required service.
This stack service is based on Valkey and keeps the service-specific setup for WordPress in one place.
Version policy
Available versions include 8.1, 7.2.
Inclusion
Enabled by default: Yes
Required: No
Primary: No
Connections
No explicit service links are defined for this stack service.
Storage
This stack service does not define persistent volume sizes.
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.