Additional database versions, trigger deployment and notification in logs view, completed Kube upgrade 1.30

Hello Team,

Take a look at this week’s changelog featuring some exciting updates and enhancements from our team!

#New database versions: PostgreSQL 17, MongoDB 8 and MySQL 8.4

We’re excited to announce support for the latest versions of popular databases:

• PostgreSQL 17
• MongoDB 8
• MySQL 8.4 (available in container mode only)

#Log view - deployment action button and new deployment notification

We’ve improved the deployment log view to make it more efficient and user-friendly.

• Deployment Button: Trigger or cancel deployments directly from the log view. No need to switch back and forth between the service list page and the log interface—saving you time and clicks.
• New Deployment Notification: If a new deployment starts while you’re reviewing logs, you’ll receive a notification within the interface. This feature ensures you’re always looking at the latest deployment logs without confusion.

#Kubernetes upgrade to 1.30 completed

The upgrade to Kubernetes 1.30 for all production clusters has been finalized! 🎉

Additionally, we’ve introduced a new guardrail to our upgrade process. Clusters will no longer upgrade if any currently deployed service relies on a Kubernetes API slated for deprecation in the next version.

What’s Next?

Our team plans to start upgrading clusters to Kubernetes 1.31 in January. We’ll share the exact timeline and details closer to the release.

#Minor Changes:

• Pod Sidebar in Logs: A few minor bug fixes and performance improvements have been delivered.
• Buildpack Support Removed: Following the decommissioning of Buildpack support, we’ve completely removed its codebase and cleaned up the interface for a sleeker experience.

For the latest news and upcoming features, remember to check out changelog.qovery.com.

As always, we appreciate your feedback and support.

Happy Deploying!

The Qovery Team 🚀