NGINX Ingress migration update, Road to Kubernetes 1.34 and 1.35, Terraform improvements

Hey Team,

‍

This one is a small milestone for us. You are reading our 100th Qovery changelog.

One hundred releases later, the goal remains the same: continuously improve the platform so teams can run Kubernetes in production without carrying the operational burden that usually comes with it. Each changelog reflects the work happening behind the scenes to make infrastructure simpler, safer, and more developer friendly.

Thank you for building with us and for all the feedback that helps shape Qovery.

Now let’s look at what shipped this week.

🔄 NGINX Ingress to API Gateway migration update

As previously announced, the community NGINX Ingress Controller will reach end of maintenance by March 2026. To prepare for this transition, Qovery is migrating from the NGINX Ingress Controller based on the Kubernetes Ingress API to Envoy Gateway built on the Kubernetes Gateway API.

The rollout is progressing well. Around 30 percent of our customers are already testing the new API Gateway and Envoy based routing layer.

We created a dedicated migration guide that explains what will change, when it will happen, and what actions may be required on your side to ensure your services continue running smoothly.

You can read the full migration guide and plan here. We have been working on implementing the last features for our customer's edge cases and the plan might change a little bit in the upcoming days, we'll share some news as soon as we can.

🚀 Road to Kubernetes 1.34 and 1.35

Upgrading Kubernetes might look like a routine version bump, but in reality it requires a large amount of preparation.

Every upgrade means verifying compatibility across Helm charts, infrastructure components, networking layers, and managed services. Our team performs extensive testing to validate configurations, identify edge cases, and prepare safe rollout strategies across all customer clusters.

This is exactly the kind of operational complexity Qovery was designed to remove from engineering teams.

As part of our regular platform maintenance cycle, we have already started preparing the next Kubernetes upgrades to versions 1.34 and 1.35. The rollout will begin next month, and we will share the detailed plan shortly.

For now, everything is being handled behind the scenes so your teams can stay focused on building and shipping applications.

🌱 Terraform improvements

We shipped a couple of improvements to make Terraform workflows inside Qovery more reliable and easier to automate.

Output validation

Qovery now validates Terraform outputs after execution to ensure they match the expected format. For example, outputs cannot start with reserved prefixes like QOVERY_.

Repository commit actions

You can now define what action should happen when a new commit is pushed to the linked Git repository. For instance, you can automatically run a plan, apply changes directly or skip depending on your workflow.

🛠️ Minor updates

• Copilot improvements: shorter and more concise responses, Mermaid diagrams generated only when necessary

• Doppler integration fix: environment variables now appear correctly as separate entries

‍