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
revealaccess 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
Declare templates in your Pulumi programs
Configuration
The defaultvalues.yaml for this template:
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 bothrequirepassandmasterauthin the Redis configuration.sentinel.password— Optional separate password for Sentinel-to-Sentinel communication (requirepasson 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-serverfor 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. customdown-after-millisecondsorfailover-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).
| Workload | Ports |
|---|---|
| Redis | 6380, 6381, … (one per replica across all locations) |
| Sentinel | 26380, 26381, … (one per location) |
firewall.externalInboundAllowCIDR must be set when public access is enabled. Without it, inbound external traffic will be blocked.
Connecting externally:
Firewall
A single firewall configuration applies to both the Redis and Sentinel workloads.firewall.internalAllowType— Controls which workloads can connect internally:
| Value | Description |
|---|---|
same-gvc | Allow access from all workloads in the same GVC (recommended) |
same-org | Allow access from all workloads in the same organization |
workload-list | Allow access only from specific workloads listed in workloads |
firewall.workloads— List of specific workload links, used wheninternalAllowTypeisworkload-list.firewall.externalInboundAllowCIDR— Comma-separated list of CIDRs allowed to reach the workloads externally. Required when public access is enabled. Use0.0.0.0/0to 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):mymaster.
Ports
| Workload | Port | Protocol | Description |
|---|---|---|---|
| Redis | 6379 | TCP | Redis data port (internal) |
| Sentinel | 26379 | TCP | Sentinel discovery port (internal) |
| Redis (public) | 6380, 6381, … | TCP | One port per replica across all locations |
| Sentinel (public) | 26380, 26381, … | TCP | One 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.provider—awsorgcp.backup.resources.cpu/backup.resources.memory— Resources for the backup cron container.
AWS S3
Before enabling backup withprovider: aws, complete the following in your AWS account:
- Create an S3 bucket. Set
backup.aws.bucketto its name andbackup.aws.regionto its region. - If you do not have a Cloud Account set up, refer to the docs to Create a Cloud Account. Set
backup.aws.cloudAccountNameto its name. - Create an IAM policy with the following JSON, replacing
YOUR_BUCKET_NAME:
- Set
backup.aws.policyNameto the name of the policy created in step 3. - Set
backup.aws.prefixto the folder path where backups will be stored.
GCS
Before enabling backup withprovider: gcp, complete the following in your GCP account:
- Create a GCS bucket. Set
backup.gcp.bucketto its name. - If you do not have a Cloud Account set up, refer to the docs to Create a Cloud Account. Set
backup.gcp.cloudAccountNameto its name. - Add the Storage Admin role to the GCP service account associated with the Cloud Account.
- Set
backup.gcp.prefixto 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://....
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