[Yandex Cloud documentation](../index.md) > [Yandex Managed Service for Valkey™](index.md) > Release notes

# Yandex Managed Service for Valkey™ release notes

## May 2026 {#may-2026}

* Added the ability to [create and restore](operations/cluster-backups.md) clusters with encrypted local disks from a backup. The encryption uses a custom KMS key.
* Maximum local disk size per host is increased to 36 TB. Disks of this size are available for Intel Ice Lake (`standard-v3`) configurations with 16 or more cores. To create extra large clusters, you may need to contact [support](https://center.yandex.cloud/support) to reserve the required resources.
* Published the updated [versioning policies](concepts/update-policy.md) detailing the terms and conditions of support for various DBMS versions.
* A new [Valkey-Search](concepts/modules.md#valkey-search) version is out: 1.2.0.
* A new [Valkey-Bloom](concepts/modules.md#valkey-bloom) version is out: 1.0.1.
* Added support for authorization with an [IAM token](../iam/concepts/authorization/iam-token.md).

## April 2026 {#apr-2026}

* You can now view Valkey™ [module](concepts/modules.md) versions (`version`).
* Added the `failover_type` field for the manual cluster switch method (`StartFailover`) to select the operation type.
* Added stable [FQDNs](concepts/network.md#hostname) for clusters: created three CNAME records in `c-{cid}-valkey{0,1,2}.db.yandex.net` format pointing to cluster hosts distributed across different availability zones and shards. The records are automatically updated when the topology changes, such as when adding or removing hosts or shards, and are available from any host.
* Published the [Valkey™ versioning policy](concepts/update-policy.md).

## March 2026 {#mar-2026}

* Added specific [roles](security/index.md) to view and edit (reschedule) [maintenance](concepts/maintenance.md) without access to the cluster.

## February 2026 {#feb-2026}

* A new [Valkey-Search](concepts/modules.md#valkey-search) version is out: 1.1.0.
* A new [Valkey-JSON](concepts/modules.md#valkey-json) version is out: 1.0.2.

## January 2026 {#jan-2026}

Added the **Shards** tab to **Monitoring**. From this tab, you can track metrics for each individual shard and promptly detect problematic nodes.

## December 2025 {#dec-2025}

* Added [detailed metrics](operations/monitoring.md#hosts) for disk usage on cluster hosts.
* Added execution details for [operations on the cluster](operations/cluster-list.md#list-operations).
* All new clusters are created with a [Connection Manager connection](../metadata-hub/concepts/connection-manager.md) by default.

## November 2025 {#nov-2025}

Added the `managed-redis.restorer` role for restoring clusters from backups. To learn more, see [Access management](security/index.md#managed-redis-restorer).

## October 2025 {#oct-2025}

* A new version is out: Valkey™ 9.0. For more information about the updates, see [this Valkey™ guide](https://github.com/valkey-io/valkey/releases/tag/9.0.0).
* Added support for:
    * [Valkey-Search](concepts/modules.md#valkey-search): Vector and full-text search.
    * [Valkey-JSON](concepts/modules.md#valkey-json): Native support for JSON documents.
    * [Valkey-Bloom](concepts/modules.md#valkey-bloom): Probabilistic data structures.
* When [creating](operations/user-create.md) a Valkey™ user, you can now immediately specify their permissions. Do it with the help of an [ACL](https://valkey.io/topics/acl/) (Access Control List) which controls the user's permissions to run particular commands.
* Added integration with Connection Manager. This tool allows you to connect to the cluster without directly using a password, thus reducing the risk of it being compromised.
* Added the ability to restore a sharded cluster from a backup.
* Added new [host classes](concepts/instance-types.md) on AMD Zen 4 and AMD Zen 4 HighFreq platforms.

## July 2025 {#jul-2025}


* Now you can [encrypt storage disks](concepts/storage.md#disk-encryption) with a custom KMS key when creating a cluster and restoring it from a backup.
* Added support for persistence [on replicas only](concepts/replication.md#persistence-on-replicas).


## May 2025 {#may-2025}

A new version is out: Valkey™ 8.1. For more information about the updates, see [this Valkey™ guide](https://github.com/valkey-io/valkey/releases).

## April 2025 {#apr-2025}

A new version is out: Valkey™ 8.0. For more information about the updates, see [this Valkey™ guide](https://github.com/valkey-io/valkey/releases).

## December 2024 {#dec-2024}

The service migrated to [Valkey™](https://valkey.io/) DBMS, an open-source fork of Redis.

## September 2024 {#sep-2024}

* A new Redis version is out: 7.2. For information about the updates, see [this Redis guide](https://raw.githubusercontent.com/redis/redis/7.2/00-RELEASENOTES).
* Redis 6.2 and 7.0 are no longer supported. Creating clusters of these versions is no longer available. One month after the release of Redis 7.2, existing Redis 6.2 and Redis 7.0 clusters were automatically upgraded to Redis 7.2.

## February 2024 {#feb-2024}

[Sharding](concepts/sharding.md) can now be enabled on existing clusters.

## Q1 2023 {#q1-2023}

* A new version is out: Redis 7.0. For information about the updates, see [this Redis guide](https://raw.githubusercontent.com/redis/redis/7.0/00-RELEASENOTES).
* Added the `rdsync` integration for improved [fault tolerance](concepts/replication.md#availability) of Redis 7.0 clusters.

## Q2 2022 {#q2-2022}

* Redis 5.0 and 6.0 are no longer supported. Creating clusters of these versions is no longer available. One month after the release of Redis 7.0, existing Redis 5.0 and Redis 6.0 clusters were automatically upgraded to Redis 6.2.
* In Terraform, added the `replica_priority` and `assign_public_ip` settings.
* Fixed the error where you could not use Terraform to manage the maintenance window.
* You can now change the `client-output-buffer-limit` normal and pub/sub settings. For more information, see the [redis.conf](https://raw.githubusercontent.com/redis/redis/unstable/redis.conf) file description.

## Q1 2022 {#q1-2022}

* You can now create clusters with public access. You can enable or update this setting at the host level and only for clusters with TLS support.
* You can now manage persistence settings. Disabling persistence improves cluster performance but increases the risk of data loss. For more information, see [Persistence](concepts/replication.md#persistence).