Nov 17, live webinar: ECS to EKS without freezing the roadmap for a quarter
Scheduled

Kubernetes 1.37 upgrade: production clusters (EKS, AKS, Scaleway)

We will upgrade every production EKS, AKS and Scaleway Kapsule cluster managed by Qovery from Kubernetes 1.36 to 1.37. You can upgrade a cluster yourself from the Console before this date. GKE clusters stay on 1.36 until Google makes 1.37 available in its Stable channel (expected around January). We will share a separate date for them.

Monday, February 15, 2027

Through the day, cluster by cluster

Applications running at least 2 instances with liveness and readiness probes keep serving traffic. An application with a single instance can go down for a short time while we replace its node.

What we will do

  1. Check that nothing on the cluster uses a Kubernetes API removed in 1.37. If a Helm chart you deployed yourself does, we stop the upgrade of that cluster and tell you.
  2. On Scaleway, check that no CiliumNodeConfig object is still in v2alpha1. If one is, we stop the upgrade of that cluster and tell you.
  3. Upgrade the Kubernetes control plane of the cluster to 1.37, and the charts Qovery manages to compatible versions.
  4. Replace the nodes. Pods move to new nodes running 1.37 before we shut down the old ones.

What to check before the window

Before every upgrade

  • Tag your non-production clusters as non-production. We upgrade them first.
  • Run each application with at least 2 instances and liveness and readiness probes, so it stays up while we replace nodes.
  • Remove any PodDisruptionBudget that allows no disruption (for example on a single-instance application). It blocks node replacement.
  • Redeploy any service you have not redeployed within your cluster's image retention period. Otherwise it may fail to restart.
  • Make sure Helm charts you deployed yourself do not use Kubernetes APIs removed in the new version. If one does, the upgrade stops.

Kubernetes 1.37

  • Envoy Gateway Lua extensions that read files or environment variables, or use getfenv, setfenv, newproxy or module, are rejected.
  • On Bottlerocket nodes (SELinux always enforcing), pods on the same node that share a volume but run with different SELinux labels stay in ContainerCreating. Setting seLinuxChangePolicy: Recursive in the pod spec keeps the old behaviour.
  • On Scaleway, convert Cilium CiliumNodeConfig objects from v2alpha1 to v2 by hand. They are not converted automatically, and the cluster stops working if any remain. Qovery stops the upgrade and tells you if it finds one.

Full timeline

  1. Mon, 23 Nov 2026We announce the upgrades in the changelog, in a Console banner and by email to the admins of every organization with a managed cluster.
  2. Mon, 30 Nov 2026Kubernetes 1.36 becomes the default for new clusters. You can upgrade your own clusters from the Console.
  3. Thu, 10 Dec 2026We send a reminder in your shared Slack channel and post the maintenance on status.qovery.com.
  4. Mon, 14 Dec 2026All non-production clusters are upgraded to 1.36.
  5. Thu, 7 Jan 2027We send a reminder and post the maintenance on status.qovery.com.
  6. Mon, 11 Jan 2027All production clusters are upgraded to 1.36.
  7. Mon, 18 Jan 2027Kubernetes 1.37 becomes the default on EKS, AKS and Scaleway. You can upgrade your own clusters from the Console.
  8. Thu, 28 Jan 2027We send a reminder and post the maintenance on status.qovery.com.
  9. Mon, 1 Feb 2027Non-production EKS, AKS and Scaleway clusters are upgraded to 1.37.
  10. Thu, 11 Feb 2027We send a reminder and post the maintenance on status.qovery.com.
  11. Mon, 15 Feb 2027Production EKS, AKS and Scaleway clusters are upgraded to 1.37. (this page)

What to expect

Applications running at least 2 instances with liveness and readiness probes keep serving traffic. An application with a single instance can go down for a short time while we replace its node.

If you notice anything unusual during the window, tell us in your shared Slack or Microsoft Teams channel and we will look at it straight away. We post live updates on our status page.