Qovery incident

Kubernetes upgrade 1.31 - NON-PRODUCTION clusters

Minor Resolved View vendor source →

Qovery experienced a minor incident on March 3, 2025, lasting —. The incident has been resolved; the full update timeline is below.

Started
Mar 03, 2025, 08:00 AM UTC
Resolved
Mar 03, 2025, 08:00 AM UTC
Duration
—
Detected by Pingoru
Mar 03, 2025, 08:00 AM UTC

Update timeline

  1. resolved Mar 03, 2025, 08:00 AM UTC

    Type: Maintenance Duration: 2 days and 21 minutes Affected Components: Infrastructure deployment, Customer infratructure Mar 5, 08:20:31 GMT+0 - Completed - Maintenance has completed successfully. Mar 3, 08:00:00 GMT+0 - Identified - As shared in [this post](https://discuss.qovery.com/t/important-qovery-managed-kubernetes-cluster-upgrade-moving-to-1-31/6815), we will start upgrading some of your Kubernetes clusters to the new version. This week we will start by upgrading all your **NON-PRODUCTION** clusters. We do not have yet a precise time when we will trigger the update, we will keep you informed as soon as we have more visibility Mar 3, 08:00:01 GMT+0 - Identified - Maintenance is now in progress