Cluster Upgrade to v3.11.154
Scheduled Maintenance Report for OpenShift Online Starter
Completed
The fuse-ignite upgrade to OpenShift version 3.11.154 has been completed.

If you have any questions, please feel free to contact us:
https://access.redhat.com/support/policy/support_process
https://access.redhat.com/support/contact/technicalSupport

Thank you for choosing Red Hat OpenShift Dedicated,
Red Hat SRE
Posted Mar 10, 2020 - 05:05 GMT-03:00
Update
The cluster upgrade is still in progress and is taking longer than expected, current estimate for completion is 9:00 AM UTC
Posted Mar 10, 2020 - 02:49 GMT-03:00
In progress
Scheduled maintenance is currently starting. We will provide updates as necessary. If you have any questions or concerns, please contact support at https://access.redhat.com/support/contact/technicalSupport/.
Posted Mar 09, 2020 - 19:59 GMT-03:00
Update
This is a reminder regarding your upcoming scheduled maintenance on Mar 9, 2020 at 23:00 UTC. If you have any questions or concerns, please contact support at https://access.redhat.com/support/contact/technicalSupport/.
Posted Mar 09, 2020 - 19:00 GMT-03:00
Update
This is a reminder regarding your upcoming scheduled maintenance on Mar 9, 2020 at 23:00 UTC. If you have any questions or concerns, please contact support at https://access.redhat.com/support/contact/technicalSupport/.
Posted Mar 09, 2020 - 16:00 GMT-03:00
Update
This is a reminder regarding your upcoming scheduled maintenance on Mar 9, 2020 at 23:00 UTC. If you have any questions or concerns, please contact support at https://access.redhat.com/support/contact/technicalSupport/.
Posted Mar 08, 2020 - 20:00 GMT-03:00
Scheduled
The OpenShift Dedicated cluster fuse-ignite has been scheduled for upgrade from version 3.11.43 to version 3.11.154 on Mar 9, 2020.

For information on the bug fixes and minor enhancements included in this upgrade, please see:
https://docs.openshift.com/container-platform/3.11/release_notes/ocp_3_11_release_notes.html#ocp-311-asynchronous-errata-updates

What to expect during the upgrade?
The patching process is engineered to cause as little disruption as possible, but brief outages may occur during the upgrade. For short periods of time, developers may be unable to create or modify application configurations. Additionally, single-pod applications will see a brief service interruption as their pod is rescheduled to an upgraded compute node. ImageStreams will also be updated to latest, which may trigger rebuilds of applications using these images.

How does the upgrade work?
Master nodes will be upgraded in place. Then, new compute nodes will be deployed with 3.11.154. Application workloads will be rescheduled to new compute nodes. Finally, old compute nodes will be decommissioned.

What communications can I expect to receive?
The following automated notifications will be sent to keep you informed:
* A reminder 24 hrs before the upgrade begins.
* A reminder 4 hrs before the upgrade begins.
* A reminder 1 hr before the upgrade begins.
* A notification when the upgrade starts.
* A notification when the upgrade has completed.

How can I minimize downtime during the maintenance?
You can minimize impact to your applications by running them in a highly available (HA) configuration using more than one pod. For single-pod applications, a deployment strategy of 'recreate' will ensure the pod is restarted after a brief outage for migration. For more information on HA application design on OpenShift, refer to the following guide:
https://blog.openshift.com/deploying-highly-available-applications-openshift-kubernetes/
To disable automatic upgrade of applications using ImageStreams, modify the imageChangeTrigger in the application's DeployConfig or BuildConfig, and refer to the following guide:
https://docs.openshift.com/container-platform/3.11/dev_guide/deployments/basic_deployment_operations.html#image-change-trigger

Thank you for choosing Red Hat OpenShift Dedicated.
OpenShift SRE

If you have any questions, please feel free to contact us:
https://access.redhat.com/support
https://access.redhat.com/support/contact/technicalSupport/
Posted Mar 04, 2020 - 22:38 GMT-03:00
This scheduled maintenance affected: fuse-ignite (Master API Service, Application Creation Service, Docker Registry Service, etcd Service).