Hey Team,

Jira and Linear are now a trigger surface into your own infrastructure, not just a place tasks get described. This release brings Agent Triggers, and extends Qovery Copilot to cluster deployment failures, translating dense Kubernetes and cloud provider errors into a clear root cause and a fix you can act on, and in some cases apply directly, the feature we teased in our last update.

One important thing before we get into what shipped. There is also a hard deadline below on NGINX: support ends August 31, and an extended support surcharge kicks in after that if you have not migrated. Please read that section even if you skim the rest.

🎫 Jira & Linear Triggers: a new entry point into your governed infrastructure

Tag or assign a ticket to Qovery on Jira or Linear, and that ticket triggers the execution of a governed environment on your own Kubernetes cluster, the same way a webhook or an API call already can. Inside it, an agent acts on the context of that ticket, running with the prompt, the Claude or Codex API token, and the guardrails your team already configured. Qovery updates the ticket status live as it runs, and reports back through it, opening a PR when the task is a coding agent's.

The agent's configuration and the triggering logic, which Jira or Linear project to watch, live in a Blueprint you define once, so every ticket in that project picks up the same setup without anyone repeating the config by hand.

Agent Triggers is available today in closed beta. Read the full story: Stop leaving the ticket. If you are an existing customer, contact your CSM to get set up.

🩺 Cluster Troubleshoot Copilot: root cause and resolution for cluster errors

A failed service deployment already gets an AI-powered root cause and fix suggestion from Qovery Copilot. A failed cluster did not, even though diagnosing it usually takes the deepest Kubernetes and cloud provider expertise on the team.

Cluster Troubleshoot Copilot closes that gap: it reads the raw Kubernetes and cloud provider error output and turns it into a root cause and resolution in plain language, the same way it already does for service deployments. Where the fix is well defined, Copilot can apply it for you.

⚠️ NGINX end of life: August 31, 2026

We have noticed you have not migrated yet. NGINX support on Qovery clusters ends August 31, 2026. The NGINX Ingress project was archived in March 2026 and has had no security patches since April, so any vulnerability found from that point on has no upstream fix and stays exploitable for as long as NGINX keeps running on your cluster.

Starting September 1, apps still on NGINX move into extended support with a surcharge on your invoice: +15% in September, +20% in October. This is not a penalty, it reflects the extra monitoring and risk we absorb to keep an unmaintained component running safely for you. Migrating before August 31 avoids both the surcharge and the security exposure.

If anything is blocking your migration, reach out now so we have time to help. The migration guide is available here, and we are happy to jump on a call.

🛠️ Minor updates

  • Disabled TLSRoute, TCP, and UDP watch in ExternalDNS. These were causing ExternalDNS to crash on some clusters, and were not needed for how Qovery routes traffic.
  • Bumped the AWS ALB controller chart version from 1.8.x to 3.x.x, keeping clusters on a maintained release line with the latest upstream fixes.

As always, let us know what you think and what you would like to see next. If you are still on NGINX, please do not wait until August 31 to start your migration.

Talk soon, The Qovery Team 🚀