Kubernetes upgrade 1.30, Karpenter instance type filter, ALB rollout, Cluster failures emails

Hello Team,

our team is back on track and we have developed some nice changes to the platform over the past sprint. Take a look at what we have managed to deliver:

#Filter the Instance Types to be used with Karpenter

Karpenter has been a part of our platform for over six months, and now we’re taking it to the next level.

You can now restrict the types of instances Karpenter uses to deploy your applications. This feature is particularly useful if you want to:

• Reduce the number of nodes by using larger instances.
• Limit deployments to specific EC2 instance families.

Check out the quick demo below from our CEO to see it in action!

#Dev Clusters Upgraded to Kubernetes 1.30

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

Once you have validated that everything works on your non-production cluster, you can manually trigger the upgrade for your production cluster using the "Upgrade to K8s 1.30" option. This allows you to ensure everything runs smoothly with the new version before applying it to your production cluster.

If you don’t initiate the upgrade yourself, we’ll proceed with it according to the schedule shared in the forum post.

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

#ALB as default and available for prod clusters

The ALB controller feature (available only on AWS) was released a few months ago and was initially limited to non-production clusters. We’ve now updated the configuration with the following changes:

• Default Activation: ALB is now activated by default for all new customers.
• Production Cluster Support: You can now enable the ALB feature on your production clusters.

For more details, check out our official communication: ALB Controller Feature.

#Email notifications on cluster update failures

To enhance responsiveness, we’ve introduced additional email notifications for cluster-related issues. These notifications will be sent to the owner and admins of your organization in the following scenarios:

• A cluster update fails.
• Cluster credentials are no longer valid.

These updates ensure you can promptly address and resolve any issues affecting your cluster setup..

#Minor Changes:

• Use private subnet ids for existing VPC setup with EKS (AWS): You can now select private subnet IDs when configuring a cluster over an existing VPC. This is necessary to enable Karpenter and run it over fargate.
• Removed default security groups (AWS): we have removed the `default` security groups that were too permissive (allowing 0.0.0.0/0)

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 🚀