Valkey™ versioning policy
The Valkey™ versioning policy is aimed at providing users with extended support for Valkey™ versions allowing to use well-proven DBMS versions longer.
The Yandex Managed Service for Valkey™ versioning policy is based on the compatibility guarantee that allows selecting a version compatible with a specific version rather than selecting a specific Valkey™ version itself. The versioning policy applies to all new clusters created in Yandex Managed Service for Valkey™.
Note
Until the end of 2026, all clusters that had been created before this policy was introduced will have been switched to it and upgraded via maintenance tasks:
- Clusters with version
7.2: To a version compatible with Valkey™ 7.2. - Clusters with version
8.0: To a version compatible with Valkey™ 8.0. - Clusters with version
8.1: To a version compatible with Valkey™ 8.1. - Clusters with version
9.0: To a version compatible with Valkey™ 9.0.
The upgrades will run automatically during maintenance windows using scheduled tasks with 90-days advance notifications sent to the user.
Stages of the compatible version lifecycle
For every Valkey™ version that has a compatible version in the Yandex Cloud implementation, the service maintains its support for no less than the support duration of the latest compatible version as per the official Valkey™ lifecycle.
| Version stage | Description and key actions | Period |
|---|---|---|
Full support (Supported) |
The version is fully supported. Recommended for new projects. | Lasts until the support for the latest compatible version is discontinued, but no less than the official Valkey™ support for this version. |
Deprecated |
Support for the version will be discontinued soon. Creating new clusters is unavailable. The existing clusters operate normally. | Six months |
Legacy |
Support for the version was officially discontinued. Clusters operate normally, but are billed at an increased rate. Technical support is limited. | Six months |
End of life (EOL) |
Discontinued version. Technical support is not provided. Clusters operate normally, but are billed at an increased rate. | N/A |
Features for each version stage
|
Action |
Full support ( |
|
|
End of life ( |
|
Creating new clusters |
||||
|
Recovery from a backup |
||||
|
Use of existing clusters |
||||
|
Support |
limited |
|||
|
Pricing |
standard |
standard |
increased1 |
increased1 |
1 Yandex Cloud will notify you in advance when a version billing starts or about upcoming changes as per the agreement.
Version support periods
| Version type | Support period | Note |
|---|---|---|
| Compatible versions | Extended support (longer than the official Valkey™ support). Versions are automatically updated to the latest compatible one. | The support duration is until the end of support for the latest compatible version. |
| Minor versions | Automatic update | Valkey™ backward-compatibility guarantee |
| Fixed versions | Automatic update | Secure bug fixes |
Version compatibility
Currently, Yandex Managed Service for Valkey™ provides2 the following compatibility with original Valkey™ versions:
| Compatibility with a version | Actual version | Compatibility guarantee | Stage | First release date | Scheduled full support expiry date3 |
|---|---|---|---|---|---|
Valkey™ 7.2 |
Valkey™ 8.1 |
Full compatibility with version 7.2 |
Full support | 16.04.2024 | 31.03.2028 |
Valkey™ 8.0 |
Valkey™ 8.1 |
Full compatibility with version 8.0 |
Full support | 15.09.2024 | 31.03.2028 |
Valkey™ 8.1 |
Valkey™ 8.1 |
Full compatibility with version 8.1 |
Full support | 31.03.2025 | 31.03.2028 |
Valkey™ 9.0 |
Valkey™ 9.0 |
Full compatibility with version 9.0 |
Full support | 21.10.2025 | 21.10.2028 |
2 As new DBMS versions are released, information in the table will be updated.
3 Support will be discontinued no earlier than the specified date.
Key principles of the Valkey™ versioning policy
The Valkey™ versioning policy is based on the following key principles:
- Extended version support. Yandex Managed Service for Valkey™ provides time-extended Valkey™ version support, where each version is supported longer than the official period due to compatibility with new Valkey™ versions.
- Compatibility guarantee. The service provides extended support with a guarantee of full compatibility with the selected Valkey™ version.
- Proven compatibility. Each DBMS implementation by Yandex Cloud is tested for compatibility with the target version. Updates are only applied in case the tests are passed successfully and completely.
- Active participation in Valkey™ development. Yandex Cloud's commitment to Valkey™ development allows the Yandex Managed Service for Valkey™ team to have a thorough understanding of the platform and ensure compatibility based on newer and more efficient implementations.
- Automatic improvements. Users automatically get the benefits of new versions without the need to migrate.
- Security and performance. Regular updates to current versions ensure the highest security and performance.
Update policy
Yandex Managed Service for Valkey™ can automatically update Yandex Cloud's Valkey™ implementation that works on your cluster without changing the target compatibility version. Such updates include:
- Updates to newer versions with guaranteed compatibility preserved.
- Specific configuration adjustments to ensure backward compatibility.
- Compatibility mode with adapted performance parameters.
- Additional checks on the Yandex Managed Service for Valkey™ side to monitor application behavior.
Tip
When updating the DBMS implementation, the cluster's target compatibility version will not change, and your app will continue to operate without the need to modify it. If required, you can contact support for details about an update.
Discontinuation of updates
Updates of the DBMS implementation are discontinued once it becomes impossible to support compatibility with newer Valkey™ versions. In this case, the version is supported until the end of support for the latest original compatible Valkey™ version.
Notifications
Yandex Managed Service for Valkey™ will notify you in advance about upcoming changes related to the cluster’s current Valkey™ version switching to another stage:
- When your cluster's Valkey™ version switches to Deprecated (and the limitations start to apply), the service will notify you 90 days in advance that creating new clusters with this version will no longer be available and will offer you to schedule an upgrade of the existing clusters to the Valkey™ version compatible with the newer fully supported version.
- When your cluster's Valkey™ version switches to Legacy (and the increase billing rate starts to apply), the service will notify you 90 days in advance about the upcoming version support expiry and the application of an increased billing rate to such clusters.
Users will get such update notifications according to their notification settings.
Notifications about scheduled operations
The table below sets out the periods for notifying users about different types of upcoming operations with Yandex Managed Service for Valkey™ clusters.
| Type of change | Minimum notification period4 | Maximum migration period5 |
|---|---|---|
| Internal version update that requires restarting hosts. | 30 days | 90 days |
| Internal version update that does not require restarting hosts. | 3 days | 7 days |
| Internal version update that requires switching the master or blocking write operations. | 14 days | 14 days |
| Security updates (maximum severity) | 5 days | 2 days |
| Security updates (high severity) | 14 days | 14 days |
| Security updates (medium severity) | 21 days | 30 days |
| Security updates (low severity) | 28 days | 120 days |
4 Minimum number of days intervening between an upcoming operation and a notification about it from Yandex Cloud.
5 Period of time during which a user can manually reschedule the operation date via the management console.