Skip to main content

Overview

Redis Multi-Location deploys a single Redis Sentinel cluster spanning multiple Control Plane locations within one GVC. All Redis replicas across all locations belong to the same cluster — replica 0 in the first location starts as the primary, and Sentinel automatically elects a new primary from any location on failure.
This template creates a new GVC. At least 2 locations are required.

What Gets Created

  • GVC — A new GVC spanning the configured locations.
  • Stateful Redis Workload — A single cross-location Redis cluster. Replica 0 in the first location starts as the primary; all others replicate from it. Each replica gets its own persistent volume.
  • Stateful Sentinel Workload — 1 Sentinel replica per location (not configurable). Monitors the cluster and orchestrates automatic failover across locations.
  • Volume Set — Persistent storage for Redis data (configurable capacity and autoscaling).
  • Secrets — Opaque secrets for the Redis and Sentinel configurations, mounted into each container.
  • Identity & Policy — Separate identities and policies for the Redis and Sentinel workloads, each with reveal access to their respective secrets.
  • Domain (optional) — One domain per workload when public access is enabled, exposing Redis and Sentinel at the configured addresses.
  • Backup Cron Workload (optional) — A scheduled backup job that writes Redis snapshots to AWS S3 or GCS. Runs in the first configured location only.

Installation

To install, follow the instructions for your preferred method:

UI

Browse, install, and manage templates visually

CLI

Manage templates from your terminal

Terraform

Declare templates in your Terraform configurations
Pulumi Icon Streamline Icon: https://streamlinehq.com

Pulumi

Declare templates in your Pulumi programs

Configuration

The default values.yaml for this template:
gvc:
  name: my-redis-gvc
  locations: # Replica count applies to Redis workload only; Sentinel always runs 1 per location
    - name: aws-eu-central-1
      replicas: 2
    - name: aws-us-west-2
      replicas: 2
    - name: aws-us-east-1
      replicas: 2

redis:
  image: redis:7.4
  resources:
    cpu: 200m
    memory: 256Mi
  serverCommand: redis-server  # Can be overridden based on the version of redis/valkey image
  # extraArgs: "--maxmemory 200mb --maxmemory-policy allkeys-lru"
  # password: your-redis-password
  publicAccess:
    enabled: false
    address: redis.example-cpln.com
  volumeset:
    initialCapacity: 20 # GiB
    autoscaling:
      enabled: false
      maxCapacity: 100 # GiB
      minFreePercentage: 10
      scalingFactor: 1.2

sentinel:
  image: redis:7.4
  resources:
    cpu: 200m
    memory: 256Mi
  # extraArgs: "--sentinel down-after-milliseconds mymaster 5000 --sentinel failover-timeout mymaster 10000"
  # password: your-sentinel-password
  publicAccess:
    enabled: false
    address: redis-sentinel.example-cpln.com

# Applies to both Redis and Sentinel workloads
firewall:
  internalAllowType: same-gvc # options: same-gvc, same-org, workload-list
  # externalInboundAllowCIDR: "0.0.0.0/0"  # Required when publicAccess is enabled. Comma-separated list.
  # externalOutboundAllowCIDR: "0.0.0.0/0"  # Comma-separated list.
  # workloads:
  #   - //gvc/GVC_NAME/workload/WORKLOAD_NAME

backup:
  enabled: false
  image: controlplanecorporation/redis-backup:1.0
  schedule: "0 2 * * *"  # daily at 2am UTC

  resources:
    cpu: 100m
    memory: 128Mi

  provider: aws # Options: aws or gcp

  aws:
    bucket: my-backup-bucket
    region: us-east-1
    cloudAccountName: my-backup-cloudaccount
    policyName: my-backup-policy
    prefix: "redis/backups"

  gcp:
    bucket: my-backup-bucket
    cloudAccountName: my-backup-cloudaccount
    prefix: "redis/backups"

Locations

  • gvc.name — Name of the GVC to create. Must be unique within your organization if deploying multiple instances.
  • gvc.locations — List of Control Plane locations to deploy into. At least 2 locations are required.
  • locations[].name — Location identifier (e.g. aws-us-east-1).
  • locations[].replicas — Number of Redis replicas to run in that location. Sentinel always runs exactly 1 replica per location regardless of this setting.

Authentication

Authentication is disabled by default. Redis and Sentinel can be configured with independent passwords.
  • redis.password — Password applied as both requirepass and masterauth in the Redis configuration.
  • sentinel.password — Optional separate password for Sentinel-to-Sentinel communication (requirepass on the Sentinel process).

Redis

  • redis.image — Redis (or Valkey) image to use.
  • redis.resources.cpu / redis.resources.memory — CPU and memory allocated per Redis replica.
  • redis.serverCommand — Override the server command (e.g. valkey-server for Valkey images).
  • redis.extraArgs — Additional server arguments appended to the startup command.

Sentinel

Sentinel monitors the Redis primary across all locations and promotes a replica on failure. One Sentinel replica is deployed per location — this is fixed and not configurable. Quorum is calculated automatically based on the number of locations.
  • sentinel.image — Redis (or Valkey) image to use for Sentinel.
  • sentinel.resources.cpu / sentinel.resources.memory — CPU and memory allocated per Sentinel replica.
  • sentinel.extraArgs — Additional Sentinel arguments (e.g. custom down-after-milliseconds or failover-timeout).

Storage

  • redis.volumeset.initialCapacity — Initial volume size in GiB for Redis data (default 20).
  • redis.volumeset.autoscaling.enabled — Automatically expand the volume as it fills. When enabled:
    • maxCapacity — Maximum volume size in GiB.
    • minFreePercentage — Trigger a scale-up when free space drops below this percentage.
    • scalingFactor — Multiply current capacity by this factor when scaling up.

Public Access

Redis and Sentinel can be exposed over the internet via TCP using Control Plane’s domain resource with per-replica port routing.
When publicAccess is enabled, a Dedicated Load Balancer is automatically enabled on the GVC. This is required for TCP port routing and is a paid Control Plane feature.
  • redis.publicAccess.enabled — Expose Redis publicly (default: false).
  • redis.publicAccess.address — A domain you control to expose Redis (e.g. redis.your-domain.com).
  • sentinel.publicAccess.enabled — Expose Sentinel publicly (default: false).
  • sentinel.publicAccess.address — A domain you control to expose Sentinel (e.g. redis-sentinel.your-domain.com).
DNS records must be added before deploying. If ownership has not been proven, the first deploy will fail and the error message will list the exact TXT and CNAME records required. Add those records in your DNS provider, then upgrade the release to complete the deployment. Disable DNS proxying (e.g. Cloudflare’s orange cloud) — TCP traffic must pass through directly. When enabled, a Control Plane domain resource is created for each address. Port mapping is one port per replica:
WorkloadPorts
Redis6380, 6381, … (one per replica across all locations)
Sentinel26380, 26381, … (one per location)
firewall.externalInboundAllowCIDR must be set when public access is enabled. Without it, inbound external traffic will be blocked. Connecting externally:
# Redis replica 0
redis-cli -h redis.your-domain.com -p 6380 ping

# Redis replica 1
redis-cli -h redis.your-domain.com -p 6381 ping

# Sentinel replica 0 (location 0)
redis-cli -h redis-sentinel.your-domain.com -p 26380 ping

Firewall

A single firewall configuration applies to both the Redis and Sentinel workloads.
  • firewall.internalAllowType — Controls which workloads can connect internally:
ValueDescription
same-gvcAllow access from all workloads in the same GVC (recommended)
same-orgAllow access from all workloads in the same organization
workload-listAllow access only from specific workloads listed in workloads
  • firewall.workloads — List of specific workload links, used when internalAllowType is workload-list.
  • firewall.externalInboundAllowCIDR — Comma-separated list of CIDRs allowed to reach the workloads externally. Required when public access is enabled. Use 0.0.0.0/0 to allow all, or restrict to specific IP ranges.
  • firewall.externalOutboundAllowCIDR — Comma-separated list of CIDRs the workloads are allowed to connect to externally.

Connecting to Redis

All replicas across all locations belong to a single cluster and are accessible within the GVC. Replica 0 in the first configured location starts as the primary. Option 1 — Load-balanced endpoint (any replica):
RELEASE_NAME-redis.GVC_NAME.cpln.local:6379
Option 2 — Direct to a specific replica:
replica-0.RELEASE_NAME-redis.LOCATION.GVC_NAME.cpln.local:6379
replica-1.RELEASE_NAME-redis.LOCATION.GVC_NAME.cpln.local:6379
Option 3 — Via Sentinel to always write to the current primary:
MASTER_INFO=$(redis-cli -h RELEASE_NAME-sentinel.GVC_NAME.cpln.local -p 26379 SENTINEL get-master-addr-by-name mymaster)
MASTER_HOST=$(echo $MASTER_INFO | cut -d' ' -f1)
MASTER_PORT=$(echo $MASTER_INFO | cut -d' ' -f2)
redis-cli -h $MASTER_HOST -p $MASTER_PORT SET my-key "Hello world"
For Sentinel-aware clients, connect through:
RELEASE_NAME-sentinel.GVC_NAME.cpln.local:26379
The Sentinel master name is mymaster.

Ports

WorkloadPortProtocolDescription
Redis6379TCPRedis data port (internal)
Sentinel26379TCPSentinel discovery port (internal)
Redis (public)6380, 6381, …TCPOne port per replica across all locations
Sentinel (public)26380, 26381, …TCPOne port per location

Backup

Backup is disabled by default. When enabled, a cron workload runs in the first configured location only and uploads a single compressed .rdb.gz snapshot to AWS S3 or GCS. The backup image is compatible with all Redis versions.
  • backup.enabled — Enable scheduled backups.
  • backup.schedule — Cron expression for backup frequency (default: daily at 2am UTC).
  • backup.provideraws or gcp.
  • backup.resources.cpu / backup.resources.memory — Resources for the backup cron container.

AWS S3

Before enabling backup with provider: aws, complete the following in your AWS account:
  1. Create an S3 bucket. Set backup.aws.bucket to its name and backup.aws.region to its region.
  2. If you do not have a Cloud Account set up, refer to the docs to Create a Cloud Account. Set backup.aws.cloudAccountName to its name.
  3. Create an IAM policy with the following JSON, replacing YOUR_BUCKET_NAME:
{
    "Version": "2012-10-17",
    "Statement": [
        {
            "Effect": "Allow",
            "Action": [
                "s3:GetObject",
                "s3:PutObject",
                "s3:DeleteObject",
                "s3:ListBucket",
                "s3:GetObjectVersion",
                "s3:DeleteObjectVersion"
            ],
            "Resource": [
                "arn:aws:s3:::YOUR_BUCKET_NAME",
                "arn:aws:s3:::YOUR_BUCKET_NAME/*"
            ]
        }
    ]
}
  1. Set backup.aws.policyName to the name of the policy created in step 3.
  2. Set backup.aws.prefix to the folder path where backups will be stored.

GCS

Before enabling backup with provider: gcp, complete the following in your GCP account:
  1. Create a GCS bucket. Set backup.gcp.bucket to its name.
  2. If you do not have a Cloud Account set up, refer to the docs to Create a Cloud Account. Set backup.gcp.cloudAccountName to its name.
  3. Add the Storage Admin role to the GCP service account associated with the Cloud Account.
  4. Set backup.gcp.prefix to the folder path where backups will be stored.

Restoring a Backup

The backup produces a single file (redis-<timestamp>.rdb.gz). Download and decompress it, then copy it to /data/dump.rdb on the replica you want to restore and restart that replica. For GCS, replace aws s3 cp s3://... with gsutil cp gs://....
aws s3 cp s3://BUCKET_NAME/PREFIX/BACKUP_FILE.rdb.gz - \
  | gunzip > /tmp/dump.rdb

External References

Redis Documentation

Official Redis documentation

Redis Sentinel Documentation

Redis Sentinel setup and client configuration

Backup Image Source

Source code for the Redis backup container image

Redis Multi-Location Template

View the source files, default values, and chart definition