Deploy Valkey

Learn how to deploy Valkey as a Helm Release on your Kubernetes cluster using lowcloud for caching, message brokering, or session storage.

Last updated: April 8, 2026

Valkey is a high-performance, open-source in-memory key/value store that is fully compatible with Redis. With the lowcloud Helm Release, you can deploy a Valkey instance on your Kubernetes cluster.

Chart Registry: oci://registry-1.docker.io/cloudpirates/valkey

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 Valkey up and running:

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:

ParameterDescriptionDefault
image.tagValkey image version9.0.0
auth.enabledEnable authenticationtrue
auth.passwordValkey password
resources.requests.cpuCPU request50m
resources.requests.memoryMemory request128Mi
resources.limits.cpuCPU limit250m
resources.limits.memoryMemory limit256Mi
persistence.sizePersistent volume size10Gi

Step-by-Step Guide

1. Add a Service

In the lowcloud Dashboard, navigate to Add Service and select Helm Release. Search for the Valkey registry in the popup:

oci://registry-1.docker.io/cloudpirates/valkey

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. valkey-cache).

Then adjust the values.yaml to match your requirements:

auth:
  enabled: true
  password: secure-password

Tip: For additional configuration options like resources and persistence, see the Extended Values section below.

3. Start the Deployment

Open the created service and click Deploy. Wait until the label in the Dashboard changes to "Deployed" — your Valkey instance is then ready and can be used by your applications.

Extended Values

Extended configuration with CPU, memory limits, and persistent storage:

image:
  tag: "9.0.0"

auth:
  enabled: true
  password: secure-password

resources:
  requests:
    cpu: 50m
    memory: 128Mi
  limits:
    cpu: 250m
    memory: 256Mi

persistence:
  size: 10Gi

Further Reading