The following MySQL and PostgreSQL plans are now deprecated:
All of your existing database clusters with these plans are still functional and accessible to you. However, you cannot resize them. To regain access to these features, fork your database to a new cluster with a supported plan. For more detailed steps, see our guides on how to fork MySQL databases and fork PostgreSQL databases.
When creating or resizing MySQL or PostgreSQL clusters on DigitalOcean, you can now add additional storage independently from your chosen database configuration plan. This provides a more economic option for increasing storage, rather than upgrading your cluster’s entire plan.
For more details, see our guides on how to resize MySQL clusters and resize PostgreSQL clusters.
When creating a new Kubernetes cluster, you can add a free database operator (now in beta), which allows you to automatically link new databases to your cluster. For more details, see our guide.
In order to improve security, DigitalOcean no longer accepts TLS 1.0 and TLS 1.1 connections. This includes connections to www.digitalocean.com, cloud.digitalocean.com, and api.digitalocean.com.
You can now configure your MySQL, PostgreSQL, and Redis Managed Databases by making a PATCH request to /v2/databases/{database_cluster_uuid}/config. For example:
{
"config": {
"sql_mode": "ANSI,ERROR_FOR_DIVISION_BY_ZERO,NO_ENGINE_SUBSTITUTION,NO_ZERO_DATE,NO_ZERO_IN_DATE,STRICT_ALL_TABLES",
"sql_require_primary_key": true
}
}
For more details, see the full reference documentation for the managed databases API.
The database online migration feature for the MySQL, PostgreSQL, and Redis database engines no longer supports migrating databases from clusters inside of DigitalOcean to other clusters inside of DigitalOcean.
Online migration is now available for the MySQL, PostgreSQL, and Redis database engines. Online migration allows you to migrate databases from external servers or cloud providers to databases in your DigitalOcean account.
You can now remove all global SQL modes from MySQL database clusters. Global SQL modes affect the SQL syntax MySQL supports and the data validation checks it performs.
Beginning 4 June 2020, you are required to create a primary key for each new table in any DigitalOcean Managed MySQL Database to improve cluster performance.
The DigitalOcean Virtual Private Cloud (VPC) service is now available for all customers. VPC replaces the private networking service. Existing private networks will continue to function as normal but with the enhanced security and features of the VPC service. See the description of VPC features for more information.
We began the incremental release of the DigitalOcean Virtual Private Cloud (VPC) service. It will be available for all customers soon. VPC replaces the private networking service.
Released v1.12.0 of the DigitalOcean Terraform Provider. This release contains improvements to Managed Database support including a new resource for configuring trusted sources and the ability to set the global SQL mode or Redis eviction policy on a cluster. There is also a new data source for finding supported Kubernetes versions. Learn more on the Terraform Changelog.
MySQL managed database clusters now support setting the global SQL mode via the control panel and the API. See How to Set Global SQL Mode on MySQL Clusters for more information.
Managed Databases for MySQL and Redis are now available in SGP1, BLR1, and TOR1, and MySQL is now in General Availability. Learn more in the MySQL and Redis announcement blog post.
Managed Databases for MySQL and Redis in Limited Availability are now available in the AMS3, LON1, and NYC3 datacenter regions. Learn more in the MySQL and Redis announcement blog post.
Managed Databases for MySQL and Redis have been released in early availability in the NYC1, FRA1, and SFO2 datacenter regions. Learn more in the MySQL and Redis announcement blog post.