Deployment queueing, Kubernetes 1.31 upgrade, simplified AWS credentials setup

Hello Team,

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

#Queueing deployment requests

It’s finally here… you can now queue deployment requests within the same environment! 🎉

Remember the toaster message saying an action couldn’t be performed because a deployment was ongoing? That’s a thing of the past!

Now, you can trigger a new deployment within the same environment, even if another one is in progress. Every new request will be added to a queue and processed as soon as the ongoing deployment is completed.

Bonus: To speed up overall deployment time, queued requests are automatically merged into a single deployment whenever possible (if triggered by the same user and if with the same action).

Check out our quick video below!

Check our documentation here.

#Clusters upgraded to Kubernetes 1.31

Following our upgrade plan, we’ve now entered the second phase:

✅ All existing clusters have been upgraded to Kubernetes 1.31 by the Qovery team!

Next up: It’s time to upgrade our own production cluster, which is why we’ve scheduled maintenance for Monday, March 7, 2025.

📢 Check the full communication here.

See you next quarter for the upgrade to Kubernetes 1.32! 🎯

#Simplified AWS credentials configuration - Moving forward with STS

We’re making progress toward removing static AWS credentials (AWS_SECRET_ACCESS_KEY and AWS_ACCESS_KEY_ID) and transitioning to STS (AWS Security Token Service) for temporary, limited-privilege credentials.

First step: We’ve removed the requirement to create a dedicated “Admins” group in your IAM setup for Qovery users.

Important: This group is still necessary for existing clusters—don’t remove it just yet! We’ll eliminate this requirement in the future.

#Minor Changes:

• Karpenter activation fixes: we have fixed a few edge case on our front-end preventing you to activate Karpenter on your cluster.
• Credential change warning: when changing the credentials of a cluster, we have added a warning message telling you that you should also update the credentials configured in the mirroring registry.

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 🚀