Yandex Cloud
Search
Contact UsTry it for free
  • Customer Stories
  • Documentation
  • Blog
  • All Services
  • System Status
  • Marketplace
    • Featured
    • Infrastructure & Network
    • Data Platform
    • AI for business
    • Security
    • DevOps tools
    • Serverless
    • Monitoring & Resources
  • All Solutions
    • By industry
    • By use case
    • Economics and Pricing
    • Security
    • Technical Support
    • Start testing with double trial credits
    • Cloud credits to scale your IT product
    • Gateway to Russia
    • Cloud for Startups
    • Center for Technologies and Society
    • Yandex Cloud Partner program
    • Price calculator
    • Pricing plans
  • Customer Stories
  • Documentation
  • Blog
© 2026 Direct Cursus Technology L.L.C.
Yandex Managed Service for Valkey™
  • Getting started
    • All guides
      • Information about existing clusters
      • Creating a cluster
      • Updating cluster settings
      • Valkey™ version upgrade
      • Working with Valkey™ models
      • Stopping and starting a cluster
      • Managing cluster hosts
      • Migrating hosts to a different availability zone
      • Managing backups
      • Deleting a cluster
  • Access management
  • Pricing policy
  • Terraform reference
  • Monitoring metrics
  • Audit Trails events
  • Public materials
  • Release notes
  • FAQ

In this article:

  • Supported versions
  • Viewing a list of available Valkey™ versions
  • Before upgrading a version
  • Upgrading a cluster
  • Examples
  1. Step-by-step guides
  2. Clusters
  3. Valkey™ version upgrade

Valkey™ version upgrade

Written by
Yandex Cloud
Updated at February 3, 2026
  • Supported versions
    • Viewing a list of available Valkey™ versions
  • Before upgrading a version
  • Upgrading a cluster
  • Examples

You can upgrade a Yandex Managed Service for Valkey™ cluster to any supported version.

Supported versionsSupported versions

All Valkey™ versions supported in Yandex Managed Service for Valkey™ remain available as long as they are supported by the vendor. Typically, this is 24 months from the version release date. For more information, see this Valkey™ guide.

Viewing a list of available Valkey™ versionsViewing a list of available Valkey™ versions

Management console
  1. Navigate to the Yandex Managed Service for Valkey™ service.
  2. Select the cluster and click Edit.
  3. Open the list in the Version field.

Note

To specify a version number in the CLI, Terraform, and the API, add the -valkey suffix to it, e.g., 8.1-valkey.

Before upgrading a versionBefore upgrading a version

Make sure the upgrade will not disrupt your applications:

  1. Check the Valkey™ release notes to learn how upgrades may affect your applications.
  2. Try upgrading a test cluster. You can deploy it from a backup of the main cluster, if Yandex Managed Service for Valkey™ supports the Valkey™ version in the backup.
  3. Create a backup of the main cluster immediately before upgrading.

Upgrading a clusterUpgrading a cluster

Alert

  • After the DBMS upgrade, you cannot revert the cluster to the previous version.
  • Whether a Valkey™ version upgrade succeeds depends on multiple factors, including your cluster’s configuration and the nature of the stored data. We recommend that you start with upgrading a test cluster with the same data and configuration.
Management console
CLI
Terraform
REST API
gRPC API
  1. In the management console, go to the folder containing the cluster to upgrade.
  2. Navigate to the Yandex Managed Service for Valkey™ service.
  3. Select the cluster you need from the list and click Edit.
  4. In the Version field, select the new version.
  5. Click Save changes.

As soon as you run the upgrade, the cluster status will change to Updating. Wait for the operation to complete and then check the cluster version.

If you do not have the Yandex Cloud CLI installed yet, install and initialize it.

By default, the CLI uses the folder specified when creating the profile. To change the default folder, use the yc config set folder-id <folder_ID> command. You can also set a different folder for any specific command using the --folder-name or --folder-id parameter.

  1. Get the list of your Valkey™ clusters using this command:

    yc managed-redis cluster list
    
  2. Get information about the cluster in question and check its Valkey™ version in the config.version setting:

    yc managed-redis cluster get <cluster_name_or_ID>
    
  3. Start the Valkey™ upgrade:

    yc managed-redis cluster update <cluster_name_or_ID> \
      --redis-version <new_version_number>
    

    As soon as you run the upgrade, the cluster status will change to Updating. Wait for the operation to complete and then check the cluster version.

  1. Open the current Terraform configuration file describing your infrastructure.

    To learn how to create this file, see Creating a cluster.

  2. Update the version argument in the config section to specify the Valkey™ version you want to upgrade to:

    resource "yandex_mdb_redis_cluster_v2" "<cluster_name>" {
        ...
        config {
            version  = "<new_version_number>"
            ...
        }
    }
    
  3. Validate your configuration.

    1. In the command line, navigate to the directory that contains the current Terraform configuration files defining the infrastructure.

    2. Run this command:

      terraform validate
      

      Terraform will show any errors found in your configuration files.

  4. Confirm updating the resources.

    1. Run this command to view the planned changes:

      terraform plan
      

      If you described the configuration correctly, the terminal will display a list of the resources to update and their parameters. This is a verification step that does not apply changes to your resources.

    2. If everything looks correct, apply the changes:

      1. Run this command:

        terraform apply
        
      2. Confirm updating the resources.

      3. Wait for the operation to complete.

For more information, see this Terraform provider guide.

Timeouts

The Terraform provider sets the following timeouts for Yandex Managed Service for Valkey™ cluster operations:

  • Creating a cluster, including by restoring it from a backup: 15 minutes.
  • Editing a cluster: 60 minutes.
  • Deleting a cluster: 15 minutes.

Operations exceeding the timeout are aborted.

How do I change these limits?

Add the timeouts section to your cluster description, such as the following:

resource "yandex_mdb_redis_cluster_v2" "<cluster_name>" {
  ...
  timeouts {
    create = "1h30m" # 1 hour 30 minutes
    update = "2h"    # 2 hours
    delete = "30m"   # 30 minutes
  }
}
  1. Get an IAM token for API authentication and place it in an environment variable:

    export IAM_TOKEN="<IAM_token>"
    
  2. Use the Cluster.Update method and send the following request, e.g., via cURL:

    Warning

    The API method will assign default values to all the parameters of the object you are modifying unless you explicitly provide them in your request. To avoid this, list the settings you want to change in the updateMask parameter as a single comma-separated string.

    curl \
        --request PATCH \
        --header "Authorization: Bearer $IAM_TOKEN" \
        --header "Content-Type: application/json" \
        --url 'https://mdb.api.cloud.yandex.net/managed-redis/v1/clusters/<cluster_ID>' \
        --data '{
                  "updateMask": "configSpec.version",
                  "configSpec": {
                    "version": "<Valkey™_version>"
                  }
                }'
    

    Where:

    • updateMask: Comma-separated string of settings you want to update.

      Here, we provide only one setting.

    • configSpec.version: New Valkey™ version.

    You can request the cluster ID with the list of clusters in the folder.

  3. Check the server response to make sure your request was successful.

  1. Get an IAM token for API authentication and place it in an environment variable:

    export IAM_TOKEN="<IAM_token>"
    
  2. Clone the cloudapi repository:

    cd ~/ && git clone --depth=1 https://github.com/yandex-cloud/cloudapi
    

    Below, we assume that the repository contents reside in the ~/cloudapi/ directory.

  3. Call the ClusterService.Update method, e.g., via the following gRPCurl request:

    Warning

    The API method will assign default values to all the parameters of the object you are modifying unless you explicitly provide them in your request. To avoid this, list the settings you want to change in the update_mask parameter as an array of paths[] strings.

    Format for listing settings
    "update_mask": {
        "paths": [
            "<setting_1>",
            "<setting_2>",
            ...
            "<setting_N>"
        ]
    }
    
    grpcurl \
        -format json \
        -import-path ~/cloudapi/ \
        -import-path ~/cloudapi/third_party/googleapis/ \
        -proto ~/cloudapi/yandex/cloud/mdb/redis/v1/cluster_service.proto \
        -rpc-header "Authorization: Bearer $IAM_TOKEN" \
        -d '{
              "cluster_id": "<cluster_ID>",
              "update_mask": {
                "paths": [ "config_spec.version" ]
              },
              "config_spec": {
                "version": "<Valkey™_version>"
              } 
            }' \
        mdb.api.cloud.yandex.net:443 \
        yandex.cloud.mdb.redis.v1.ClusterService.Update
    

    Where:

    • update_mask: List of parameters to update as an array of strings (paths[]).

      Here, we provide only one setting.

    • config_spec.version: New Valkey™ version.

    You can request the cluster ID with the list of clusters in the folder.

  4. Check the server response to make sure your request was successful.

ExamplesExamples

Let's assume you need to upgrade your cluster version from 8.1 to 9.0.

CLI
  1. To get the list of clusters with their IDs and names, run this command:

    yc managed-redis cluster list
    

    Result:

    +----------------------+---------------+---------------------+--------+---------+
    |          ID          |     NAME      |     CREATED AT      | HEALTH | STATUS  |
    +----------------------+---------------+---------------------+--------+---------+
    | c9q8p8j2gaih******** |   redis406    | 2022-04-23 12:44:17 | ALIVE  | RUNNING |
    +----------------------+---------------+---------------------+--------+---------+
    
  2. To get information about the redis406 cluster, run the following command:

    yc managed-redis cluster get redis406
    

    Result:

    id: c9q8p8j2gaih********
    ...
    config:
      version: 8.1-valkey
      ...
    
  3. To upgrade a cluster named redis406 to version 9.0, run the following command:

    yc managed-redis cluster update redis406 --redis-version 9.0-valkey`
    

Was the article helpful?

Previous
Updating cluster settings
Next
Working with Valkey™ models
© 2026 Direct Cursus Technology L.L.C.