Event-based autoscaling, Copilot accessible to anyone, Audit Log diff viewer, TF/OTF resources

Hey Team,

This sprint brings several improvements focused on running demanding workloads in production, reducing operational overhead, and giving teams better visibility and control. From smarter autoscaling to clearer audit trails, here is what is new.

‍

⚡ Event based autoscaling with KEDA

Many production workloads cannot scale safely using CPU or memory alone. Take a billing system processing asynchronous jobs from a queue. Each worker is expected to run close to 100 percent CPU, while scaling should follow the number of pending messages, not resource usage.

With CPU based autoscaling, scaling often reacts too late. Queues grow, latency increases, and teams end up manually adjusting autoscaling rules during traffic spikes just to protect SLAs.

Qovery reduces the operational burden of running these workloads by integrating KEDA directly into application autoscaling. Qovery installs and manages KEDA for you and exposes it in the same place where you already configure scaling.

You can keep standard HPA based on CPU or memory, or switch to event driven autoscaling using custom metrics like queue depth, without turning autoscaling into a separate infrastructure project.

‍

The feature is only available on AWS EKS clusters for now and you need to contact our support to have it enabled

You can learn more in our blog article and in the official documentation.

‍

🤖 Self service Qovery AI Copilot activation

The Qovery AI Copilot is now available in beta to anyone through self service. You can enable it directly from the new AI Copilot section available in your organization settings without contacting support. Only the "Read-only" mode is available for now, we will introduce the Read-Write mode later in the quarter.

Activation only requires approving the terms and conditions. A copy is automatically sent by email for reference.

‍

From this same section, you can also view all scheduled tasks currently running or paused that the Copilot executes for you in the background. This gives full transparency over automated actions and long running operations.

🕵️ Improved audit logs with diff viewer

We significantly improved the audit log experience. Along with a refreshed design, audit logs now include a diff viewer that shows exactly what changed.

For example, when you modify a service CPU limit, you can immediately see the previous value and the new value side by side. This makes reviews, incident analysis, and compliance checks much easier.

‍

🌱 Terraform and OpenTofu resource viewer

Alongside with the generated output variables, you can now see which Terraform or OpenTofu resources have been deployed after running a manifest.

The resource view is refreshed after every successful execution and gives you a clear, up to date picture of your infrastructure state in one place, without digging through logs or external tools.

🛠️ Minor updates

‍

• Qovery Observe now supports email as an alert notification channel, in addition to Slack
• EKS migration to Karpenter is progressing and production cluster migration is ongoing

‍

That is it for this release. As always, thank you for the feedback that helps us improve Qovery sprint after sprint.

Talk soon,

The Qovery Team 🚀

‍