Replicated End of Life

Critical Considerations

Obtain a YugabyteDB Anywhere license before attempting any migration. Contact Yugabyte Support to request a license.

Description

YugabyteDB Anywhere will end support for Replicated installation at the end of 2024. This means updates will no longer be available, preventing YugabyteDB Anywhere and YugabyteDB database upgrades, in perpetuity.

Mitigation

Migrate your YugabyteDB Anywhere installation from Replicated by performing the following steps:

1. Upgrade YugabyteDB Anywhere instances to the latest v2.18 or v2.20 using Replicated.
2. Migrate from the Replicated-based install to a YBA Installer-based install using the Migration Steps.

Details

To guarantee interoperability, upgrading to a YugabyteDB Anywhere version greater than or equal to latest v2.18 may require additional actions, such as first upgrading the database cluster(s) version (also known as universes), or performing an upgrade to Docker.

For more details, refer to YugabyteDB Anywhere version compatibility with YugabyteDB.

If there are no version compatibility issues, YugabyteDB Anywhere upgrades should be performed before any additional upgrades to the database.

When performing step 1 of the mitigation, review the prerequisites for Replicated-based installs to avoid any potential upgrade issues.

Recommended upgrade path (Ideal)

Yugabyte recommends upgrading YugabyteDB Anywhere and YugabyteDB database to the latest v2.20 LTS.

Acceptable upgrade path (Satisfactory)

Important YugabyteDB release considerations

• v2.14 database releases reach End of Maintenance in July 2024, End of Life in January 2025.
• v2.16 database releases reach End of Life in June 2024.
• v2.18 database releases reach End of Life in November 2024.

For more details, refer to Releases.

Scenario 1

Suppose you are running YugabyteDB Anywhere earlier than the latest v2.18, with universes running YugabyteDB database earlier than the latest v2.14.

If you want to upgrade YugabyteDB Anywhere to the latest v2.18 or v2.20, and only upgrade database nodes to v2.14, do the following:

1. Check Replicated prerequisites.
2. Upgrade YBA to the latest version of your current branch (using Replicated).
3. Upgrade YBA to the latest v2.18 (using Replicated).
4. Upgrade YugabyteDB database nodes to latest v2.14.
5. Migrate YugabyteDB Anywhere off Replicated, to YBA Installer.
6. Plan the upgrade of database nodes prior to EOL in January 2025.

Scenario 2

Suppose you are running YugabyteDB Anywhere earlier than the latest v2.18, with universes running YugabyteDB at v2.14, v2.16, or v2.18.

If you want to upgrade YugabyteDB Anywhere to the latest v2.18 or 2.20, and leave your database on its current version, do the following:

1. Check Replicated prerequisites.
2. Upgrade YBA to the latest version of your current branch (using Replicated).
3. Upgrade YBA to the latest v2.18 or v2.20 (using Replicated).
4. Migrate YugabyteDB Anywhere off Replicated, to YBA Installer.
5. Plan the upgrade of database nodes prior to EOL for the respective versions. For more details, refer to Releases.

Minimum requirements (Sub-optimal)

Important YugabyteDB release considerations

• v2.14 database releases reach End of Maintenance in July 2024, End of Life in January 2025.
• v2.16 database releases reach End of Life in June 2024.
• v2.18 database releases reach End of Life in November 2024. For more details, refer to Releases.

Scenario

Suppose you are running YugabyteDB Anywhere v2.14, with universes running YugabyteDB nodes on v2.12.

To upgrade YugabyteDB Anywhere to the latest v2.18 or v2.20, and only upgrade your database to the latest v2.14, do the following:

1. Check Replicated prerequisites.
2. Upgrade YugabyteDB Anywhere to the latest v2.14 (using Replicated).
3. Upgrade YugabyteDB database to the latest v2.14.
4. Upgrade YugabyteDB Anywhere to the latest v2.18 or v2.20 (using Replicated).
5. Migrate YugabyteDB Anywhere off Replicated, to YBA Installer.