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

Cluster component updates: cert-manager 1.21, Karpenter 1.15

We roll out cert-manager 1.21 and Karpenter 1.15 from the week of Monday 23 November. Each cluster gets them at its next deployment, ahead of the Kubernetes 1.36 upgrade on 14 December.

Monday, November 23, 2026

From the week of 23 November, at each cluster's next deployment

Nothing Qovery manages is affected. Check only what you built yourself.

What to check before the window

cert-manager 1.21

  • Issuers you created that authenticate with the cert-manager controller's own service account (serviceAccountRef.name: cert-manager, for example Vault or Route53) can no longer issue or renew certificates. Certificates already issued keep working until they expire. Give each such issuer its own service account, Role and RoleBinding.
  • If your monitoring selects the cert-manager metrics port by name, update it. The port is renamed from tcp-prometheus-servicemonitor to http-metrics (same port number, 9402).
  • Users who create ACME Challenges, or create or change ACME Orders, through the Kubernetes edit or admin role can no longer do so.
  • Vault issuers whose spec.vault.path contains .. are rejected.

Karpenter 1.15 (EKS clusters that use Karpenter)

  • Existing nodes are not replaced.
  • Dashboards or alerts on Karpenter metrics may need an update:
    • reason is now lowercase on karpenter_nodepool_allowed_disruptions and karpenter_nodepool_nodes_consuming_budgets.
    • consolidation_type on karpenter_voluntary_disruption_queue_failures_total reports empty, single or multi.
    • error on karpenter_cloudprovider_errors_total is unknown instead of empty.
  • Karpenter node classes you created outside Qovery become NotReady if they set invalid kubelet options.

Load balancer allowed IP ranges

  • In aws.eks.alb_controller.load_balancer_source_ranges, write ranges in standard form, starting at the beginning of the range (10.0.0.0/8, not 10.0.0.1/8), and write IPv4 as IPv4, not inside IPv6. Qovery refuses other forms when the setting is saved and suggests the right one. No existing cluster needs a change.

Related maintenance

What to expect

Nothing Qovery manages is affected. Check only what you built yourself.

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.