Upgrade to 3.0

Move your data to a new MaestroHub version with the upgrade command, follow the 2.6 to 3.0 guide, and go back if something goes wrong.

Data changes

Only through the upgrade command

Upgrade from

2.6.0 to 2.6.5

Kubernetes

No upgrade path from 2.6

📄️ What Changes in 3.0

Every 2.6 behaviour that changes in 3.0, who it affects, and what to do about it before or after the upgrade.

📄️ Upgrade from 2.6.x to 3.0

Step-by-step upgrade from any 2.6 release to 3.0 for Docker Compose, Docker and single-binary installs, with what each step prints and what to do next.

📄️ How MaestroHub Keeps Upgrades Safe

What MaestroHub promises when you move to a new version, how the upgrade command works, and what it does not do.

📄️ The Upgrade Report

How to read what upgrade check and upgrade apply print, how to decide items that need a person, and the options of apply.

📄️ Going Back and Solving Problems

What to do when 3.0 shows the Data migration needed page, when apply refuses, how backup sets work, how to return to 2.6 before or after 3.0 has started, and which warnings to expect after the upgrade.

📄️ Upgrade Command Reference

The upgrade commands, their flags and their exit codes.