Manage Aiven for Valkey™ versions

Aiven for Valkey™ supports multiple versions of Valkey running concurrently in the platform. Choose a version that best fits your needs and upgrade your service when ready.

Supported Valkey versions

From version 9.0, Aiven for Valkey supports two major upstream Valkey versions at a time. These are the two latest major versions that are stable on the Aiven Platform. You can select either version when you create a service or upgrade an existing service. If you do not select a version, the default is the latest stable version on the Aiven Platform.

See the supported versions in the Aiven for Valkey version reference.

Before you upgrade

Available or upcoming upgrades

Track upgrades for your service via:

• Aiven Console: Service Overview page > Maintenance section > List of available mandatory and optional upgrades
• Email: notifications for automated upgrades

Downgrade restriction

Downgrading to a previous version is not supported due to potential data format incompatibilities. Always test upgrades in a non-production environment first.

To revert to a previous version:

1. Create a service with the desired version.
2. Restore data from a backup taken before the upgrade.
3. Update your application connection strings.

Prerequisites for upgrade

Before upgrading your service:

• Test in development: Test the upgrade in a development environment first.
• Backup your data: Ensure you have recent backups. Backups are automatic, but verify they exist.

To upgrade your service version, check that:

• Your Aiven for Valkey service is running.
• Target version to upgrade to is available for manual upgrade.
• You can use one of the following tools to upgrade:
  • Aiven Console
  • Aiven CLI
  • Aiven API
  • Aiven Provider for Terraform
  • Aiven Operator for Kubernetes®

Upgrade your service

Console

1. In the Aiven Console, go to your Valkey service.

2. On the Overview page, go to the Maintenance section.

3. Click Actions > Upgrade version.

4. Select a version to upgrade to.

   warning

   When you click Upgrade:

   • The system applies the upgrade immediately.
   • You cannot downgrade the service to a previous version.

5. Click Upgrade.

CLI

Upgrade the service version using the avn service update command:

avn service update SERVICE_NAME -c valkey_version="N.N"

Parameters:

• SERVICE_NAME: Name of your service
• N.N: Target service version to upgrade to, for example 9.0

API

Call the ServiceUpdate endpoint to set valkey_version:

curl --request PUT \
  --url https://api.aiven.io/v1/project/PROJECT_NAME/service/SERVICE_NAME \
  --header 'Authorization: Bearer BEARER_TOKEN' \
  --header 'Content-Type: application/json' \
  --data '{
    "user_config": {
      "valkey_version": "N.N"
    }
  }'

Parameters:

• PROJECT_NAME: Name of your project
• SERVICE_NAME: Name of your service
• BEARER_TOKEN: Your API authentication token
• N.N: Target service version to upgrade to, for example 9.0

Terraform

Use the aiven_valkey resource to set valkey_version:

resource "aiven_valkey" "example" {
  project      = var.PROJECT_NAME
  cloud_name   = "CLOUD_NAME"
  plan         = "PLAN_NAME"
  service_name = "SERVICE_NAME"

  valkey_user_config {
    valkey_version = "N.N"
  }
}

Parameters:

• PROJECT_NAME: Name of your project
• CLOUD_NAME: Cloud region identifier
• PLAN_NAME: Service plan
• SERVICE_NAME: Name of your service
• N.N: Target service version to upgrade to, for example 9.0

Kubernetes

Use the Valkey resource to set valkey_version:

apiVersion: aiven.io/v1alpha1
kind: Valkey
metadata:
  name: SERVICE_NAME
spec:
  authSecretRef:
    name: aiven-token
    key: token

  connInfoSecretTarget:
    name: valkey-connection

  project: PROJECT_NAME
  cloudName: CLOUD_NAME
  plan: PLAN_NAME

  userConfig:
    valkey_version: "N.N"

Apply the updated configuration:

kubectl apply -f valkey-service.yaml

Parameters:

• PROJECT_NAME: Name of your project
• SERVICE_NAME: Name of your service
• CLOUD_NAME: Cloud region identifier
• PLAN_NAME: Service plan
• N.N: Target service version to upgrade to, for example 9.0

Version selection for new services

When creating an Aiven for Valkey service:

• Default version: The latest stable version on the Aiven Platform is the default version.
• Explicit selection: You can specify a version using the valkey_version parameter.
• Version availability: Only versions in available state can be selected.

Example (CLI):

avn service create SERVICE_NAME \
  --service-type valkey \
  --plan PLAN_NAME \
  --cloud CLOUD_NAME \
  -c valkey_version="N.N"

Parameters:

• SERVICE_NAME: Name of your service
• PLAN_NAME: Service plan
• CLOUD_NAME: Cloud region identifier
• N.N: Service version, for example 8.1

Related pages