> For the complete documentation index, see [llms.txt](https://academy.cegedim.cloud/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://academy.cegedim.cloud/databases/valkey/valkey-upgrade.md).

# Valkey - Upgrade

## **PaaS upgrade workflow** <a href="#valkeyupgradeinplace-valkeypaasupgrade" id="valkeyupgradeinplace-valkeypaasupgrade"></a>

### Request <a href="#valkeyupgradeinplace-request" id="valkeyupgradeinplace-request"></a>

The update of a Valkey PaaS is the responsibility of cegedim.cloud and can be requested via a request ticket submitted from ITCare.

Please specify a time slot to execute the upgrade and if the operation is to be carried out outside of business hours.

It is recommended that you upgrade your non-production environments first in order to estimate the downtime generated by the operation and to test your applications using the new engine version.

### Process <a href="#valkeyupgradeinplace-process" id="valkeyupgradeinplace-process"></a>

The upgrade of a Valkey deployment (standalone or high availability cluster) takes place in two fully automated steps:

* Update the operating system first if required
  * Multiple updates depending on the scenario: Debian X → Debian Y
* Update of the Valkey and Sentinel engine in the specified target version

```mermaid
graph TD
    start["Valkey X<br/>Debian X"] --> debian["Upgrade Debian<br/>(once or not required)"]
    debian --> valkey["Upgrade Valkey agent"]
    valkey --> sentinel["Upgrade Sentinel agent<br/>(if needed)"]
    sentinel --> done["Valkey Y<br/>Debian Y"]

    debian -.->|Handled by cegedim.cloud| sentinel

    style start fill:#e8e8e8,stroke:#000,stroke-width:2px,color:#000
    style debian fill:#ffe0b2,stroke:#e8820c,stroke-width:2px,color:#000
    style valkey fill:#c8e6c9,stroke:#2ca02c,stroke-width:2px,color:#000
    style sentinel fill:#c8e6c9,stroke:#2ca02c,stroke-width:2px,color:#000
    style done fill:#e8e8e8,stroke:#000,stroke-width:2px,color:#000
```

{% hint style="info" %}
Depending on the source and target versions of Valkey, it may be necessary to first migrate the operating system to a version supported by cegedim.cloud (for more information, check OS / Valkey support matrix below).
{% endhint %}

### Impacts

The duration of an update is variable and depends on:

* The topology
  * Standalone topology: Valkey will be upgraded.
  * Sentinel topology: Valkey and Sentinel on all nodes will be upgraded.
* The amount of operating system upgrade necessary

### Time references

* Debian operating system upgrade: 10 minutes on average
* Valkey package upgrade : 5 minutes on average
* Sentinel package upgrade: 5 minutes on average

## OS / Valkey support matrix

Linux distributions supported by cegedim.cloud depending on the Valkey version:

| Valkey version | Debian version |
| -------------- | -------------- |
| 8.1.x          | Debian 12      |
| 9.1.x          | Debian 13      |

{% hint style="info" %}
To upgrade from Valkey 8.1 to Valkey 9.1, a prior operating system upgrade from Debian 12 to Debian 13 will be required, as it is the only supported version for Valkey 9.1. This step is handled by cegedim.cloud and is carried out before the Valkey engine upgrade.
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://academy.cegedim.cloud/databases/valkey/valkey-upgrade.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
