Kubernetes upgrade 1.29, New deployment log view, Whitelist on Kube public endpoint, new AWS regions

Hello Team,

This week, our team is enjoying an autumn retreat in Lille, France, spending quality time together after releasing some exciting features over the past two weeks. Check them out:

#Non-production Clusters Upgraded to Kubernetes 1.29

As mentioned in this forum thread, we’ve upgraded your non-production Managed clusters to Kubernetes version 1.29.

Now, it’s time to upgrade your production clusters. The upgrade will be triggered on October 28th. If this timeline doesn’t suit you, feel free to manually trigger the upgrade beforehand using the "Upgrade K8s to 1.29" button.

For those using our Self-Managed solution, please update the version of your Qovery charts by running the qovery cluster install command, and then upgrade your Kubernetes cluster version.

#New deployment log view

We’ve revamped the deployment log view to improve clarity and visibility:

• Deployment Pipeline: You now have a global view of each stage in the deployment pipeline and their status.
• Separation of Deployment vs. Running Logs: We’ve replaced the tab system with two distinct views to display deployment logs and application logs for each service.
• Deployment Time: You can now clearly see the deployment time for each service, along with the time spent on each step (build, deploy, etc.).
• Pre-Checks Step: This has always been part of the process, but is now more clearly visible in the interface.

Check out the video below!

#Enable Whitelist on Kubernetes Public Endpoints

We've introduced new advanced settings that allow you to restrict access to the public endpoints of your Kubernetes clusters on AWS and GCP. This is especially useful for compliance concerns, as it ensures that only a specific set of whitelisted IPs can access the public endpoints. You can manage this feature via the advanced settings `qovery.static_ip_mode` and `k8s.api.allowed_public_access_cidrs`.

#New AWS Regions Available

We’ve expanded our list of supported AWS regions for Managed clusters, now including:

• Asia Pacific (Hyderabad) ap-south-2
• Europe (Spain) eu-south-2
• UAE me-central-1

#Minor Changes:

• Renamed advanced settings database.xxx.deny_public_access: we've renamed this advanced settings into database.xxx.deny_any_access.

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 🚀