Upgrade is complete, the cluster is showing stable for the last few hours.
Oct 6, 04:16 CEST
We have completed applying updates and doing the final reboots of all systems. We will monitor the cluster for a while longer before calling this emergency maintenance concluded.
Oct 6, 02:08 CEST
All compute node updates have been finished - Based on monitoring all sites are back online again. We're conducting the post upgrade checks at the moment.
Oct 5, 23:20 CEST
We will continue with the OpenShift upgrade of the compute nodes
Oct 5, 19:58 CEST
Control Plane update is fully done now and the cluster is stable. We'll move on to upgrading the compute nodes after 8pm CEST in order to move the emergency maintenance further out of business hours.
Oct 5, 18:09 CEST
We're conducting checks after the control plane upgrade and assess on when to continue with the upgrade.
Oct 5, 16:37 CEST
Sites start to come back online. We're monitoring the situation.
Oct 5, 16:13 CEST
We're continuing to investigate the issue that causes the routes to fail.
Oct 5, 16:01 CEST
We're seeing the issues with sites being down. We're investigating.
Oct 5, 15:57 CEST
The control plane upgrade looks good. There could be intermittent deployment errors during the upgrade. Get in touch with our engineers and we'll be looking into the issue.
Oct 5, 15:44 CEST
We found a small issue during the control plane upgrade which has been fixed - carrying on with the control plane upgrade.
As soon as we finish this part we'll carry on and update the compute nodes. We'll update here as soon as this will start.
During the compute node upgrade there might happen short downtimes due to the restart of the containers.
Oct 5, 14:51 CEST
Control Plane update is still running - We'll update as soon as new information becomes available.
Oct 5, 13:38 CEST
Control Plane update is currently running. We expect small <1min downtimes and will take action if needed.
Oct 5, 12:35 CEST
Pre-maintenance tasks have been completed sucessfully.
We plan to start the first part of the OpenShift upgrade momentarily.
Downtimes should be minimal (< 1 minute) . Our engineers are monitoring the situation closely and take action if needed.
Oct 5, 11:30 CEST
amazee.io had planned to upgrade the ch1.lagoon cluster on October 11, 2018. However, due to persistent issues being experienced on the cluster, we have decided to trigger an emergency maintenance window, and begin upgrading the cluster immediately. We believe that this will bring stability to the cluster, and resolve the issues being experienced by a number of our customers.
Our team is currently polishing the plans for the upgrade, and will post a follow up as soon as we have solidified the strategy and timeline for the upgrade.
We are sorry for any inconvenience this may cause, and would like to assure our customers that we are doing everything within our power to keep downtime to an absolute minimum.
If you need any further information, our engineering team are available on Slack & Rocketchat. You are also welcome to reach out to us via email using email@example.com
Oct 5, 11:19 CEST