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
Agentic Kubernetes resource reclamation is the practice of using an autonomous control plane to continuously identify, suspend, and delete idle infrastructure across a multi-cloud Kubernetes fleet. It replaces manual cleanup and reactive autoscaling with intent-based policies that act on business state, eliminating the configuration drift and cloud waste typical of unmanaged fleets.
Kubernetes is an open-source platform that automates the deployment, scaling, and management of containerized applications. While originally designed to orchestrate single-cluster workloads, modern enterprise use cases require managing Kubernetes at fleet scale, coordinating thousands of clusters across multi-cloud environments to enforce cost governance, security policies, and automated lifecycle management.
The shift from AI copilots to autonomous agents is redefining infrastructure requirements. Discover how to build secure, stateful, and compliant Agentic AI systems using Kubernetes, sandboxing, and observability while meeting EU AI Act standards
Effective Kubernetes management in 2026 demands a shift from manual cluster building to intent-based fleet orchestration. By implementing agentic automation on standard EKS, GKE, or AKS clusters, enterprises eliminate operational weight, prevent configuration drift, and proactively control cloud spend without vendor lock-in, enabling effective scaling across massive fleets.
A Kubernetes single pane of glass is a centralized management layer that unifies visibility, access control, cost allocation, and policy enforcement across § cluster in an enterprise fleet for all cloud providers. It replaces the fragmented practice of switching between AWS, GCP, and Azure consoles to govern infrastructure, giving platform teams a single source of truth for multi-cloud Kubernetes operations.
Deploying a Docker container on Kubernetes requires building an image, authenticating with a registry, writing YAML deployment manifests, configuring services, and executing kubectl commands. While necessary to understand, executing this manual workflow across thousands of clusters causes severe configuration drift. Enterprise platform teams use agentic platforms to automate the entire deployment lifecycle.
At enterprise scale, managing provider-specific Kubernetes YAML across multiple clouds creates crippling configuration drift and operational toil. By adopting an agentic Kubernetes management platform, infrastructure teams abstract cloud-specific configurations (like ingress controllers and storage classes) into a single, declarative intent that automatically reconciles across 1,000+ clusters.
To stop GPU costs from destroying SaaS margins, teams must transition from static to consumption-based infrastructure by utilizing Karpenter for dynamic provisioning, maximizing hardware density with NVIDIA MIG, and leveraging Qovery to tie scaling directly to business metrics.
.webp)