Description

Ensure every Public Cloud Database service runs an engine version, such as PostgreSQL, MySQL, or MongoDB, that is still supported by OVHcloud and its vendor, and is upgraded before end of life.

Rationale

Unsupported database versions stop receiving security fixes, leaving known vulnerabilities open, and may be forcibly upgraded or removed by the provider. Running supported versions keeps the database patched and avoids unplanned upgrades.

Impact

  • The database keeps receiving security fixes

  • Avoids forced upgrades at end of life

  • Upgrades must be tested for application compatibility

Default Value

Services stay on the version they were created with until they are upgraded.

Pre-Requisites

  • Permission to manage the database service

  • Applications tested against the new version

  • A recent backup

Test Plan

  1. Log in to the OVHcloud Control Panel at https://www.ovh.com/manager/.

  2. In the left-hand menu, select Public Cloud and choose your project.

  3. In the left-hand menu, select Databases (under Databases & Analytics), then click the database service to open it.

  4. On the Dashboard tab, check the engine version.

  5. Compare it with OVHcloud's supported versions for that engine.

  6. If the version is end of life or close to it, follow the implementation steps.

Implementation Steps

  1. Log in to the OVHcloud Control Panel at https://www.ovh.com/manager/.

  2. In the left-hand menu, select Public Cloud and choose your project.

  3. In the left-hand menu, select Databases (under Databases & Analytics), then click the database service to open it.

  4. Upgrade the version from the service settings if the engine supports in-place upgrades.

  5. Otherwise, create a new service on a supported version, migrate the data, and switch the applications.

  6. Test the applications after the upgrade.

Backout Plan

  1. Restore the backup taken before the upgrade to a new service on the previous version if needed.

Reference