Deploy Redis
Last updated: March 16, 2026
Redis is a fast, open-source in-memory data store commonly used as a cache, message broker, or session store. With the lowcloud Helm Release, you can deploy a Redis instance on your Kubernetes cluster.
Chart Registry: oci://registry-1.docker.io/cloudpirates/redis
The Helm Release is provided and maintained by Cloud Pirates.
Prerequisites
- A lowcloud account with an active cluster
- Access to the lowcloud Dashboard
Quick Start
Minimal configuration to get Redis up and running:
architecture: standalone
auth:
enabled: true
password: secure-password
Tip: Always use a strong password and change the default values before deploying.
Configuration
Here are the most important configuration options:
| Parameter | Description | Default |
|---|---|---|
architecture | Redis architecture (standalone or replication) | standalone |
auth.enabled | Enable authentication | true |
auth.password | Redis password | — |
persistence.enabled | Enable persistent storage | true |
persistence.size | Persistent volume size | 2Gi |
resources.requests.cpu | CPU request | 50m |
resources.requests.memory | Memory request | 128Mi |
Step-by-Step Guide
1. Add a Service
In the lowcloud Dashboard, navigate to Add Service and select Helm Release. Search for the Redis registry in the popup:
oci://registry-1.docker.io/cloudpirates/redis
Then select the desired Helm Release version. The "latest" option is a good choice in most cases.
2. Configure Values
Give the Helm service a descriptive name in lowcloud (e.g. redis-cache).
Then adjust the values.yaml to match your requirements:
architecture: standalone
auth:
enabled: true
password: secure-password
Tip: For additional configuration options like resources and persistence, see the Values with Resources section below.
3. Start the Deployment
Open the created service and click Deploy. Wait until the label in the Dashboard changes to "Deployed" — your Redis instance is then ready and can be used by your applications.
Extended Values
Extended configuration with CPU, memory limits, and persistent storage:
architecture: standalone
auth:
enabled: true
password: secure-password
persistence:
enabled: true
size: 2Gi
resources:
limits:
cpu: 200m
memory: 256Mi
requests:
cpu: 50m
memory: 128Mi