Migrate from DigitalOcean Redis to Valkey #3
Description
Issue Description
DigitalOcean has announced the deprecation of their Managed Redis service and introduced Managed Caching for Valkey as the replacement. According to their blog post, Redis will have an end-of-availability (EOA) date of April 30, 2025, after which no new Redis clusters can be created.
Background
- Valkey is a Redis-compatible, open-source key-value datastore that serves as a drop-in replacement for Redis
- Existing Redis clusters will continue to operate after the EOA date, but migration is encouraged
- Valkey is fully compatible with Redis 7.2.4 and offers enhanced features
Required Changes
1. Terraform Configuration
Update the Redis resource in infra/main.tf (lines 114-123):
- Change
engine = "redis"toengine = "valkey" - Update resource name from
redistovalkeyfor clarity - Consider updating version to "8" (Valkey 8.0) from "7" (Redis 7)
2. Update References
The following files reference Redis and need updates:
infra/outputs.tf- Update output nameshelm/echo/templates/_helpers.tpl- Environment variable referenceshelm/echo/templates/deployment-directus.yaml- Redis environment variablessecrets/sealed-backend-secrets-*.yaml- REDIS_URL references (may need regeneration)README.md- Documentation updates
3. Migration Steps
For existing environments:
- Development Environment: Create new Valkey cluster and migrate data
- Production Environment: Plan migration window with minimal downtime
- Use DigitalOcean's migration tools as documented here
Benefits of Migration
- Continued support and updates from DigitalOcean
- Enhanced features including:
- Per-slot metrics for better observability
- Multi-threading capabilities
- Dual-channel replication
- Experimental RDMA support
Timeline
- April 29, 2025: Last day to create new Redis clusters
- April 30, 2025: Redis EOA date
- Recommend completing migration before end of March 2025