-
Notifications
You must be signed in to change notification settings - Fork 258
fix(red): upgrade #5668
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
fix(red): upgrade #5668
Changes from 1 commit
Commits
Show all changes
3 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
85 changes: 85 additions & 0 deletions
85
pages/managed-databases-for-redis/api-cli/upgrade-redis-version.mdx
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,85 @@ | ||
| --- | ||
| title: How to upgrade the version of your Redis™ Database Instance | ||
| description: Steps to upgrade the version of your Redis™ Database Instance on Scaleway. | ||
| tags: managed-database redis database version upgrade | ||
| dates: | ||
| validation: 2025-10-15 | ||
| --- | ||
| import Requirements from '@macros/iam/requirements.mdx' | ||
|
|
||
| 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. | ||
|
|
||
| <Message type="important"> | ||
| - 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/). | ||
| </Message> | ||
|
|
||
| <Requirements /> | ||
|
|
||
| - A Scaleway account logged into the [console](https://console.scaleway.com) | ||
| - [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization | ||
| - A valid [API key](/iam/how-to/create-api-keys/) | ||
| - [Configured your environment variables](https://github.com/scaleway/scaleway-cli/blob/master/docs/commands/config.md) (optional) | ||
| - 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. | ||
ldecarvalho-doc marked this conversation as resolved.
Outdated
Show resolved
Hide resolved
|
||
|
|
||
|
|
||
| You can list your Database Instances to determine which ones need to be updated. | ||
|
|
||
| 1. Run the following command. Replace the values with your corresponding information if you have not set environment variables. | ||
|
|
||
| ```bash | ||
| curl -X GET | ||
| -H "Content-Type: application/json" \ | ||
| -H "X-Auth-Token: $SCW_SECRET_KEY" https://api.scaleway.com/redis/v1/zones/$SCW_ZONE/clusters | ||
| ``` | ||
|
|
||
| You should get a response like the following, where each `cluster` corresponds to a Redis™ Database Instance. | ||
| ```json | ||
| { | ||
| "clusters": [ | ||
| { | ||
| "id": "string", | ||
| "name": "string", | ||
| "project_id": "string", | ||
| "status": "string", | ||
| "version": "string", | ||
| "endpoints": [ ], | ||
| "tags": [], | ||
| "node_type": "string", | ||
| "created_at": "string", | ||
| "updated_at": "string", | ||
| "tls_enabled": "boolean", | ||
| "cluster_settings": [], | ||
| "acl_rules": [], | ||
| "cluster_size": "integer", | ||
| "zone": "string", | ||
| "user_name": "string", | ||
| "upgradable_versions": [] | ||
| } | ||
| ], | ||
| "total_count": "integer" | ||
| } | ||
| ``` | ||
| 2. Make note of the ID(s) of the Instance(s) you want to upgrade. | ||
|
|
||
| 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). | ||
|
|
||
| 3. Run the following command. Make sure you replace `{cluster_id}` with the ID of your Database Instance. | ||
|
|
||
| <Message type="note"> | ||
| 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. | ||
| </Message> | ||
|
|
||
| ```bash | ||
| curl -X POST \ | ||
| -H "X-Auth-Token: $SCW_SECRET_KEY" https://api.scaleway.com/redis/v1/zones/{zone}/clusters/{cluster_id}/migrate \ | ||
| -H "Content-Type: application/json" \ | ||
| -d '{ | ||
| "version": "7.2.11" | ||
| }' | ||
| ``` | ||
|
|
||
| If the operation is successful you will see the configuration of your Instance, with the updated version. | ||
|
|
||
| <Message type="note"> | ||
| 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. | ||
| </Message> | ||
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Uh oh!
There was an error while loading. Please reload this page.