AKS Managed by Qovery in Beta, Kubernetes 1.32/1.33 upgrade plan, Bitnami catalog change

Hello Team,

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

#Azure AKS managed by Qovery is now available in Open Beta

We’re excited to announce that the Qovery Managed cluster offering now officially supports Microsoft Azure AKS (Azure Kubernetes Service), making it easier than ever to deploy and manage cloud-native applications on Azure with zero Kubernetes overhead.

This is now available in open Beta!

From day one, Qovery’s mission has been to simplify Kubernetes operations and deployment across cloud providers, thanks to our Managed offer. After solidifying our support for AWS EKS and Google GKE, Azure AKS was the natural next step and one of the most requested features from our community.

With Qovery + AKS you will get:

• No Kubernetes expertise needed
• Get fully managed cluster operations, including automated upgrades
• Enjoy sensible defaults and built-in automation for configuration, networking, and secrets
• Built-in high availability with multi-zone AKS cluster support
• Stay secure with automatic secret and credential rotation
• Manage your infrastructure across AWS, GCP, and Azure in one unified platform
• Compliance SOC2 HIPAA (Coming soon)
• Advanced autoscaler Karpenter (Coming soon)

Have a look at our official announcement

#Upgrade plan available for Kubernetes 1.32/1.33

As part of our regular maintenance cycle, we’ve published the full plan for upgrading your clusters to Kubernetes 1.32 and 1.33.

You can find the complete details in this forum post, but here’s a quick recap of the timeline:

1.31 → 1.32

• 19/08/2025: All newly created clusters will run Kubernetes 1.32 by default
• 19/08/2025: Cluster upgrade becomes available to users
• 25/08/2025: Upgrade of all non-production clusters to 1.32
• 08/09/2025: Upgrade of all production clusters to 1.32

1.32 → 1.33

• 15/09/2025: All newly created clusters will run Kubernetes 1.33 by default
• 15/09/2025: Cluster upgrade becomes available to users
• 22/09/2025: Upgrade of all non-production clusters to 1.33
• 06/10/2025: Upgrade of all production clusters to 1.33

Upgrading Kubernetes might look simple on the surface, but it’s far from it. Behind the scenes, it takes a full month of focused engineering work to validate and prepare every component across all clusters.

Each upgrade requires:

• Reviewing and upgrading all Helm charts for compatibility
• Testing integrations with managed services
• Validating cluster-specific configurations
• Planning and executing safe, phased rollouts

This is exactly why we roll out upgrades to non-production clusters first, giving you time to validate everything before we touch production.

#Bitnami catalog changes: what you need to know

Bitnami recently announced that many of its free container images will move to a legacy repository with no future updates. If you want to use the latest, secure versions of these images, you’ll now need to subscribe to their paid plan.

This change impacts both Qovery-managed workloads and customer-deployed applications relying on Bitnami charts. We’ve already reviewed our internal usage and are updating our stacks accordingly.

If your apps rely on Bitnami images, we’ve proactively reached out to let you know, along with recommendations to avoid potential issues in the future.

#Minor Changes:

• Improved message during cluster delete: when there is a dependency violation during the cluster delete, we have improved the error message to let you know which dependency is blocking the operation.
• Fixed CLI temp directory cleanup: fix available in CLI 1.40.5

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 🚀