Say Goodbye to Digital Ocean: Major Change in Supported Cloud Providers
After a lot of thought and consideration, we've decided to say goodbye to Digital Ocean. While we loved having them on board, the truth is, we have super high standards when it comes to the cloud service providers we support. We want to make sure that our users can run their production workloads with confidence and without any hiccups. Unfortunately, since we started offering Digital Ocean in December 2020, we've had some issues and outages that just didn't meet our expectations.
Now, we know that transparency is important to you, and it's important to us too. That's why we put so much effort into running thousands of tests to make sure that the cloud service providers we support are up to snuff. In this case, Digital Ocean just wasn't cutting it. But don't worry, we're hoping to bring them back in the future once we have the right infrastructure in place.
In the meantime, we've got some great news to share! We're expecting to start offering official support for both Google Cloud Platform and Azure later this year! We don't have a set date yet, but we'll keep you in the loop through our public roadmap.
Now, we know that changes can be a bit of a hassle, but don't worry - you don't have to do anything! We've already stopped serving Digital Ocean and have been asking our users to move their workloads over to either AWS or Scaleway. We're confident that these two cloud service providers will provide the infrastructure and support that you need. And if you have any questions or concerns, our support team is here to help!
Thanks for being a part of the Qovery community. We're always here to help, so don't hesitate to reach out if you need anything.
Cheers, The Qovery Team
.svg)
.svg)
.svg)
Suggested articles
Kubernetes success is determined by Day 2 execution, not Day 1 deployment. While migration is a bounded project, maintenance is an infinite loop that often consumes 40% of senior engineering capacity. To protect margins and velocity, enterprises must transition from manual toil to agentic automation that handles scaling, security, and cost.
Day-0 is planning, Day-1 is deployment, and Day-2 is the infinite lifecycle of maintenance. While Day-0/1 are foundational, Day-2 is where enterprise operational debt accumulates. At fleet scale (1,000+ clusters), managing these differences manually is impossible, requiring agentic automation to maintain stability and eliminate toil.
A multi-cluster Kubernetes architecture distributes application workloads across geographically separated clusters rather than a single environment. This strategy strictly isolates failure domains, ensures regional data compliance, and guarantees global high availability, but demands centralized Day-2 control to prevent exponential cloud costs and operational sprawl.
Stop overpaying for Kubernetes observability. Learn how in-cluster monitoring and AI-driven troubleshooting with Qovery Observe can eliminate APM ingestion fees, reduce SRE bottlenecks, and make your cloud costs predictable.
Kubernetes multi-cluster management is the Day-2 operational practice of orchestrating applications, security, and configurations across geographically distributed clusters. Because native Kubernetes was designed for single-cluster orchestration, enterprise platform teams must implement a centralized control plane to prevent configuration drift and manage a global fleet without scaling manual toil.
Achieving zero-downtime deployments on Kubernetes requires more than running multiple pods. It demands a standardized architecture utilizing Pod Disruption Budgets (PDBs), precise liveness and readiness probes, pod anti-affinity, and graceful termination handling. At an enterprise scale, these configurations must be enforced via a centralized control plane to prevent catastrophic configuration drift.
.webp)