Yandex Cloud
Search
Contact UsGet started
  • Blog
  • Pricing
  • Documentation
  • All Services
  • System Status
    • Featured
    • Infrastructure & Network
    • Data Platform
    • Containers
    • Developer tools
    • Serverless
    • Security
    • Monitoring & Resources
    • ML & AI
    • Business tools
  • All Solutions
    • By industry
    • By use case
    • Economics and Pricing
    • Security
    • Technical Support
    • Customer Stories
    • Start testing with double trial credits
    • Cloud credits to scale your IT product
    • Gateway to Russia
    • Cloud for Startups
    • Education and Science
    • Yandex Cloud Partner program
  • Blog
  • Pricing
  • Documentation
© 2025 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
      • Stopping and starting a cluster
      • Managing cluster hosts
      • Migrating hosts to a different availability zone
      • Managing backups
      • Deleting a cluster
  • Access management
  • 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 a version upgrade
  • Upgrading a cluster
  • Examples
  1. Step-by-step guides
  2. Clusters
  3. Valkey™ version upgrade

Valkey™ version upgrade

Written by
Yandex Cloud
Updated at May 13, 2025
  • Supported versions
    • Viewing a list of available Valkey™ versions
  • Before a version upgrade
  • Upgrading a cluster
  • Examples

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

Supported versions

All Valkey™ versions, which were supported in Yandex Managed Service for Valkey™, will remain available as long as the vendor continues to support them. Normally, this is for 24 months after a version is released. For more information, see the relevant Valkey™ documentation.

Viewing a list of available Valkey™ versions

Management console
  1. In the management console, navigate to the folder page and select Yandex Managed Service for Valkey™.
  2. Select a cluster and click Edit.
  3. Open the list in the Version field.

Before a version upgrade

Make sure this does not affect your applications:

  1. See Valkey™ changelog for how upgrades may affect your applications.
  2. Try a version upgrade on a test cluster. You can deploy it from a backup of the main cluster, provided Yandex Managed Service for Valkey™ supports the Valkey™ version in the backup.
  3. Create a backup of the main cluster directly before the version upgrade.

Upgrading a cluster

Alert

  • After updating the DBMS, the cluster cannot be rolled back to the previous version.
  • The success of a Valkey™ version upgrade depends on multiple factors, including cluster settings and data stored in databases. We recommend that you begin by upgrading a test cluster that has the same data and settings.
Management console
CLI
Terraform
REST API
gRPC API
  1. In the management console, go to the folder containing the cluster to upgrade.
  2. Select Yandex Managed Service for Valkey™.
  3. Select the cluster 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) command line interface yet, install and initialize it.

The folder specified when creating the CLI profile is used by default. To change the default folder, use the yc config set folder-id <folder_ID> command. You can specify a different folder using the --folder-name or --folder-id parameter.

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

    yc managed-redis cluster list
    
  2. Get information about the cluster you need and check the Valkey™ version in the config.version parameter:

    yc managed-redis cluster get <cluster_name_or_ID>
    
  3. Run 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 that defines your infrastructure.

    For more information about creating this file, see Creating clusters.

  2. Under config, change the version parameter to the Valkey™ version you want to upgrade to.

    resource "yandex_mdb_redis_cluster" "<cluster_name>" {
        ...
        config {
            version  = "<new_version_number>"
            ...
        }
    }
    
  3. Make sure the settings are correct.

    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 the Terraform provider documentation.

Time limits

A Terraform provider sets the timeout for Yandex Managed Service for Valkey™ cluster operations:

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

Operations exceeding the set timeout are interrupted.

How do I change these limits?

Add the timeouts block to the cluster description, for example:

resource "yandex_mdb_redis_cluster" "<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 put it into the 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: List of parameters to update as a single string, separated by commas.

      Only one parameter is provided in this case.

    • configSpec.version: New Valkey™ version.

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

  3. View the server response to make sure the request was successful.

  1. Get an IAM token for API authentication and put it into the 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 the repository contents are stored in the ~/cloudapi/ directory.

  3. Use the ClusterService.Update call and send the following request, e.g., via gRPCurl:

    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 paths[] strings.

      Only one parameter is provided in this case.

    • config_spec.version: New Valkey™ version.

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

  4. View the server response to make sure the request was successful.

Examples

Let's assume you need to upgrade your cluster from version 7.0 to version 7.2.

CLI
  1. To retrieve a list of clusters and find out their IDs and names, run the command below:

    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 a cluster named redis406, run the following command:

    yc managed-redis cluster get redis406
    

    Result:

    id: c9q8p8j2gaih********
    ...
    config:
      version: "7.0"
      ...
    
  3. To upgrade a cluster named redis406 to version 7.2, run the following command:

    yc managed-redis cluster update redis406 --redis-version 7.2
    

Was the article helpful?

Previous
Updating cluster settings
Next
Stopping and starting a cluster
© 2025 Direct Cursus Technology L.L.C.