New deployment history view, Customize error pages, upcoming Kubernetes 1.31

Hello Team,

Check out this week’s changelog for exciting updates and enhancements from our team!

#New deployment history view

We’ve revamped the deployment history view for both environments and services to provide greater visibility into:

• The entire deployment pipeline
• Deployment times
• Who triggered the deployment and how

This update makes it easier to track and manage deployments efficiently!

Coming soon: You’ll also be able to manage the deployment queue directly from this section. Stay tuned!

#Customize the error pages of your application

By default, when your service is not reachable or encounters issues, generic error pages are returned to the end user (e.g., "404 Not Found" or "503 Service Unavailable"). These pages are managed by the NGINX Ingress controller, they are functional but lack branding or contextual information, which can be a poor user experience for end-users.

Thanks to our latest developments, you can now create custom error pages and deploy them directly with Qovery.

Check out our complete guide here

#Preparing for the upgrade to Kubernetes 1.31

We have begun preparations for the upgrade to Kubernetes 1.31. In this forum post, you’ll find all the information you need, including:

• How the upgrade is managed

• The upgrade plan (starting with non-prod, then prod)

• What actions you need to take

#Minor Changes:

• Deployment history log breadcrumb: we have added a fallback mechanism on the breadcrumb showing the deployment history in case there are no deployments available.
• Added info on debug pod for self-managed cluster: We have added in the dropdown a section describing how to connect remotely to your cluster via the Qovery remote bug.

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 🚀