Skip to content

Commit c0186c4

Browse files
fix(red): upgrade
1 parent cdf7714 commit c0186c4

File tree

2 files changed

+90
-1
lines changed

2 files changed

+90
-1
lines changed
Lines changed: 85 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,85 @@
1+
---
2+
title: How to upgrade the version of your Redis™ Database Instance
3+
description: Steps to upgrade the version of your Redis™ Database Instance on Scaleway.
4+
tags: managed-database redis database version upgrade
5+
dates:
6+
validation: 2025-10-15
7+
---
8+
import Requirements from '@macros/iam/requirements.mdx'
9+
10+
Scaleway supports the latest version of Redis™ (7.2.11). Follow the steps below to upgrade your Database Instance's to the latest Redis™ version.
11+
12+
<Message type="important">
13+
- We recommend you use the latest available version of Redis (7.2.11) with your Database Instances to avoid the vulnerabilities identified in the [Redis™' Security Advisory: CVE-2025-49844](https://redis.io/blog/security-advisory-cve-2025-49844/).
14+
</Message>
15+
16+
<Requirements />
17+
18+
- A Scaleway account logged into the [console](https://console.scaleway.com)
19+
- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization
20+
- A valid [API key](/iam/how-to/create-api-keys/)
21+
- [Configured your environment variables](https://github.com/scaleway/scaleway-cli/blob/master/docs/commands/config.md) (optional)
22+
- Make sure you check that your upgrade path is [supported by Redis™](https://redis.io/docs/latest/operate/rs/references/upgrade-paths/). If it is not supported, you will need to first upgrade to a supported intermediate version.
23+
24+
25+
You can list your Database Instances to determine which ones need to be updated.
26+
27+
1. Run the following command. Replace the values with your corresponding information if you have not set environment variables.
28+
29+
```bash
30+
curl -X GET
31+
-H "Content-Type: application/json" \
32+
-H "X-Auth-Token: $SCW_SECRET_KEY" https://api.scaleway.com/redis/v1/zones/$SCW_ZONE/clusters
33+
```
34+
35+
You should get a response like the following, where each `cluster` corresponds to a Redis™ Database Instance.
36+
```json
37+
{
38+
"clusters": [
39+
{
40+
"id": "string",
41+
"name": "string",
42+
"project_id": "string",
43+
"status": "string",
44+
"version": "string",
45+
"endpoints": [ ],
46+
"tags": [],
47+
"node_type": "string",
48+
"created_at": "string",
49+
"updated_at": "string",
50+
"tls_enabled": "boolean",
51+
"cluster_settings": [],
52+
"acl_rules": [],
53+
"cluster_size": "integer",
54+
"zone": "string",
55+
"user_name": "string",
56+
"upgradable_versions": []
57+
}
58+
],
59+
"total_count": "integer"
60+
}
61+
```
62+
2. Make note of the ID(s) of the Instance(s) you want to upgrade.
63+
64+
To upgrade to a more recent version of Redis™, you can use the [migrate endpoint](https://www.scaleway.com/en/developers/api/managed-databases-for-redis/#path-redistm-database-instance-scale-up-a-redistm-database-instance).
65+
66+
3. Run the following command. Make sure you replace `{cluster_id}` with the ID of your Database Instance.
67+
68+
<Message type="note">
69+
Since we use a POST type call, you only need to edit the parameter that defines the version, the other confguration of your Database Instance will remain the same.
70+
</Message>
71+
72+
```bash
73+
curl -X POST \
74+
-H "X-Auth-Token: $SCW_SECRET_KEY" https://api.scaleway.com/redis/v1/zones/{zone}/clusters/{cluster_id}/migrate \
75+
-H "Content-Type: application/json" \
76+
-d '{
77+
"version": "7.2.11"
78+
}'
79+
```
80+
81+
If the operation is successful you will see the configuration of your Instance, with the updated version.
82+
83+
<Message type="note">
84+
If your Database Instance is in standalone mode, there might be a few seconds of downtime while the Instance upgrades. For High Availability and Cluster modes, the upgrade is performed first on secondary nodes, then the main node. When the main node is upgraded, one of the secondary nodes takes over automatically to reduce downtime.
85+
</Message>

pages/managed-databases-for-redis/menu.ts

Lines changed: 5 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -64,6 +64,10 @@ export const managedDatabaseRedisMenu = {
6464
label: 'Using Publish/Subscribe messaging',
6565
slug: 'using-pub-sub-feature',
6666
},
67+
{
68+
label: 'Upgrade your Redis™ version',
69+
slug: 'upgrade-redis-version',
70+
}
6771
],
6872
label: 'API/CLI',
6973
slug: 'api-cli',
@@ -77,7 +81,7 @@ export const managedDatabaseRedisMenu = {
7781
{
7882
label: 'Ensuring data persistence',
7983
slug: 'ensuring-data-persistence',
80-
},
84+
}
8185
],
8286
label: 'Additional Content',
8387
slug: 'reference-content',

0 commit comments

Comments
 (0)