Valkey Release Notes
Last verified 10 Jul 2026
June 2026
30 June
-
DigitalOcean Managed Valkey database clusters now support custom CNAME records, allowing clients to connect through your own hostname instead of the default
*.db.ondigitalocean.comaddress. Custom CNAMEs are available through the API when creating clusters or when updating an existing cluster, and apply to the public network connection only. For more information, see Configure Custom CNAMEs for Valkey.
January 2026
8 January
-
The Network Access tab for managed databases now shows a resource type icon next to each trusted source, so you can distinguish sources that share the same display name, such as a Droplet and a tag. When you add trusted sources with Quick select, the dropdown also groups resources by type. To add trusted sources, see our guides for PostgreSQL, MySQL, MongoDB, Valkey, OpenSearch, and Kafka.
May 2025
16 May
-
New managed database clusters are now automatically provisioned with default alert policies for CPU, memory, and disk utilization at a 90% threshold. These alerts notify you via email when resource usage is high, so you can investigate your application load or scale your cluster. You can modify or remove the default alerts at any time. For more information, see the following:
7 May
-
You can now manually convert your Caching cluster to a Valkey cluster. All Caching clusters automatically convert to Valkey clusters by the Managed Caching discontinuation date.
April 2025
30 April
-
DigitalOcean Managed Caching is being discontinued on 30 June 2025.
To replace Managed Caching, we are offering Managed Valkey, a Redis-compatible alternative with RDMA and higher throughput. All existing Managed Caching clusters automatically convert to Valkey clusters by 30 June 2025 during your upgrade window, retaining all data.