Enable Karpenter on existing prod clusters, Activate S3 audit logging , upcoming Kubernetes 1.31

Hello Team,

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

#Enable Karpenter on existing production clusters

We’ve enabled the option to activate Karpenter on existing production clusters.

Important Requirement

To enable Karpenter, your cluster must have the "Static IP / NAT Gateway" feature enabled. Here’s why:

• Karpenter runs on a Fargate node, requiring a private subnet and a NAT gateway to function properly.
• Without this feature, only one NAT gateway will be deployed in a single zone.
• If that zone experiences an issue, your cluster won’t be able to run Karpenter, preventing it from scaling your production environment up or down.

Future Improvements

We’re working on a way to enable Karpenter on existing production clusters without requiring a NAT gateway, but this won’t be available until next year.

If you need Karpenter immediately, you’ll need to migrate your applications to a new cluster with the NAT gateway feature enabled.

#Activate S3 audit logging

In line with SOC2 compliance recommendations, we’ve introduced a new feature that allows you to enable S3 audit logging on your cluster.

How to Enable It

You can activate this feature easily by:

• Updating the advanced settings: Set object_storage.enable_logging to true.
• Re-deploying your cluster.

This enhancement helps improve security and compliance effortlessly.

#Preparing for the upgrade to Kubernetes 1.31

As outlined in our forum post, we’ve now moved into the first phase of the upgrade plan:

• Every new cluster created via Qovery now runs Kubernetes 1.31 by default.
• You can manually upgrade your existing cluster or wait for the scheduled upgrade (March 3 → Non-production clusters, March 10 → Production clusters)

Stay tuned for further updates, and refer to the forum post for more details!

#Minor Changes:

• Build target selection available in the API: if you have a multi-stage docker file, you can now select the target stage. This feature is only available via the API and it will be soon available in the UI as well.
• Return info in case of env var conflict: when adding a new environment variable and a conflict is detected, we return now the name of the service/env/project where the environment variable already exists.

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 🚀