Skip to main content

Upgrade from Aiven for Caching to Aiven for Valkey™

Upgrade your Aiven for Caching service to Aiven for Valkey using the Aiven Console or Aiven API. The process retains configurations, users, and data without disrupting your service.

Prerequisites​

  • Ensure your Aiven for Caching service is running version 7.2. Upgrade to 7.2 if needed.
  • To upgrade using the Aiven API, ensure you have an Aiven API token with the necessary permissions.

What to expect during the upgrade​

  • No service disruption: The upgrade occurs without interruption. The service is recycled, and the nodes are replaced, but your service continues to operate during the process.
  • DNS updates: DNS names update to new hosts during the upgrade. This might cause brief delays as the changes take effect, but the service remains available.
  • Automatic configuration transfer: All Aiven for Caching configurations are automatically updated to work with Aiven for Valkey. No manual changes are needed.
note

After you upgrade to Aiven for Valkey, you cannot revert to Aiven for Caching.

Upgrade service​

  1. Access the Aiven Console and select your Aiven for Caching service.
  2. Click Service settings.
  3. Go to Service management section, and click Actions > Upgrade to Valkey.
  4. On the confirmation window, review the upgrade process guidelines, and click Confirm upgrade.

After confirming, the Service status changes to Rebalancing in the Service settings screen. This indicates that the upgrade is in progress. The nodes are recycled, and your service continues to operate as the upgrade completes.

Learn how to update Terraform configuration and state after upgrading to Valkey™.