TF/OpenTofu Support, RDS Monitoring, NGINX ingress end of life

Hey Team,

We have a big set of updates this sprint that all point in the same direction: simplify your platform, remove unnecessary tools, and give you better visibility over what really matters.

Let’s jump in.

‍

🚀 Stop tool sprawl with Terraform and OpenTofu support

Provisioning cloud resources should not require a second stack of tools. With Qovery’s new Terraform and OpenTofu support, you can now define and deploy your infrastructure right alongside your applications with no glue required.

You can:

Specify deployment order between infrastructure resources and applications
Pass Terraform outputs as environment variables to your workloadsManage the full stack lifecycle directly inside Qovery
Run everything securely inside your Kubernetes cluster

Teams that previously juggled multiple systems to provision resources can now keep everything in one place with a consistent workflow from code to cloud.

Below a quick video to show you how it works:

‍

Check our announcement article here or our public documentation to know more.

‍

📊 RDS monitoring is now available in Qovery Observe

Starting today, you get full visibility over your RDS databases directly inside Qovery. Troubleshoot app and database issues in one place without bouncing between different dashboards or opening the AWS console.

Qovery centralizes observability with deployment and provisioning, giving developers a single place to diagnose issues quickly. Since Qovery already manages RDS provisioning with almost no friction, adding RDS monitoring directly in the product was the natural next step.

‍
You can now view CPU, memory, disk usage, and other technical metrics from RDS alongside your Kubernetes workload logs. This makes it much easier to understand the full story behind an incident.

‍

⚠️ NGINX Ingress Controller end of maintenance by March 2026

For years, the community ingress-nginx controller has served as the default entry point for routing traffic in Kubernetes clusters. It is widely adopted across companies of every size.

However, maintainers have announced that the project will move into end of life mode by March 2026, with parts of the ecosystem already deprecated or archived. This has serious implications for teams relying on it in production.

At Qovery we will migrate to the Gateway API and adopt Envoy Gateway as the new routing layer.

Here is what it means for you:

If your Kubernetes clusters are managed by Qovery

Nothing to do on your side. Qovery will replace ingress-nginx in Q1 2026 with the new routing system based on the Gateway API. The migration will be seamless, with no downtime.

If you use self-managed Kubernetes clusters

Reach out to your Customer Success Manager. We will review your setup and support your migration plan.

‍

🛠️ Minor updates

Qovery Copilot: fixed Marmaid display issue
ALB Controller: increased to two replicas to reduce failures
Cluster stop: Added automatic scale down on Karpenter node pools when a cluster is stopped to reduce cost

‍

That is all for this sprint. If you want more details or have suggestions, we are always happy to hear from you.

Talk soon,

The Qovery Team 🚀

‍