What changed
DigitalOcean’s current Managed MySQL documentation says MySQL 8.0 clusters are scheduled for forced upgrades to MySQL 8.4 beginning October 30, 2026, with the work performed during each cluster’s configured maintenance window. DigitalOcean began offering MySQL 8.4 for new clusters on May 19 and now states that 8.4 is the only supported MySQL series. Its managed-update documentation says software updates cannot be disabled: the platform creates an updated cluster, replicates data, switches DNS to the new cluster and may change the underlying IP address. DigitalOcean says the update process is designed for no downtime, although brief periods of latency can occur. Oracle supports the 8.0-to-8.4 LTS upgrade path but explicitly recommends compatibility checks and application testing before major-version upgrades.
Why it matters
A managed database reduces patching work, but it also transfers control over when unsupported software is retired. DigitalOcean users still on MySQL 8.0 have a fixed date by which application compatibility, changed defaults, removed features, spatial indexes, drivers and operational assumptions should be tested against 8.4. The provider-controlled migration can also change the cluster’s underlying IP address, so applications or firewall rules that depend on fixed addresses rather than DNS deserve attention. The update being designed for zero downtime does not make a major database-version change behaviorally risk-free.
The October 30 date is a forced-upgrade boundary
DigitalOcean lists the MySQL 8.0 retirement under Upcoming Changes and says forced upgrades to MySQL 8.4 will begin October 30 during each cluster’s maintenance window. Operators can configure the maintenance window and may manually initiate available updates, but DigitalOcean’s managed-update policy says software updates required for security and stability cannot be disabled.
The managed update swaps the backing cluster
DigitalOcean documents its software-update process as creating a replacement cluster with the operating-system or database-engine update applied, replicating the existing data and then switching DNS. The underlying IP address can change. DigitalOcean says this process has no planned downtime, but there can be brief latency during the maintenance window.
MySQL supports the upgrade path, but compatibility still needs checking
Oracle lists 8.0-to-8.4 as a supported LTS upgrade path and recommends running the MySQL Shell Upgrade Checker, reviewing incompatible changes and changed defaults, testing applications in a non-production environment and benchmarking representative workloads. MySQL 8.4 is an LTS line, but the first release of an LTS series can add or remove features compared with the previous LTS.
The practical migration work sits above the managed database
DigitalOcean handles the database-engine upgrade itself, but it cannot validate every application query, ORM, connector, schema assumption or operational integration. Teams should exercise their own workload against an 8.4 cluster before the forced window and make sure monitoring, firewall rules and connection handling follow the managed hostname rather than an underlying address.