pro-eu-west-1 upgrade to 3.11
Scheduled Maintenance Report for OpenShift Online Pro
Completed
Cluster upgrade to 3.11 for pro-eu-west-1 has been successfully completed.

Thank you for using OpenShift.

Support links:
https://access.redhat.com/support
https://access.redhat.com/support/contact/technicalSupport/
Posted 18 days ago. Nov 29, 2018 - 06:07 UTC
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 19 days ago. Nov 28, 2018 - 14:02 UTC
Update
This is a reminder regarding your upcoming scheduled maintenance on Nov 28, 2018 at 14:00 UTC. If you have any questions or concerns, please contact support at https://access.redhat.com/support/contact/technicalSupport/.
Posted 19 days ago. Nov 28, 2018 - 13:00 UTC
Update
This is a reminder regarding your upcoming scheduled maintenance on Nov 28, 2018 at 14:00 UTC. If you have any questions or concerns, please contact support at https://access.redhat.com/support/contact/technicalSupport/.
Posted 19 days ago. Nov 28, 2018 - 10:00 UTC
Update
This is a reminder regarding your upcoming scheduled maintenance on Nov 28, 2018 at 14:00 UTC. If you have any questions or concerns, please contact support at https://access.redhat.com/support/contact/technicalSupport/.
Posted 19 days ago. Nov 28, 2018 - 06:00 UTC
Scheduled
The pro-eu-west-1 is scheduled for the upgrade to 3.11 starting Nov 28, 2018 at 14:00 UTC and ending at approximately 05:00 UTC on Nov 29, 2018.

The maintenance process is engineered to disrupt applications as little as possible, but brief outages may occur during the process.

For short periods of time, developers may be unable to create new applications or interact with existing applications.

How does the upgrade work?
The master nodes will be upgraded first, and then new nodes will be deployed with 3.11. Application workloads will then be migrated to those new nodes and finally the legacy nodes will be decommissioned.

The following imagestreams will be updated:
dotnet-rhel7
dotnet-runtime-rhel7
eap-cd-openshift-rhel7
nodejs-rhel7
eap-cd-basic-s2i
eap-cd-postgresql-persistent-s2i

To disable automatic upgrade of these applications, modify the imageChangeTrigger in the application's DeployConfig or BuildConfig.

https://docs.openshift.com/container-platform/3.9/dev_guide/deployments/basic_deployment_operations.html#image-change-trigger

You can minimize the impact on your applications by scaling your services to more than one (1) pod. In general, for applications to be able to continue to service clients, they should be scaled. Some pod workloads are not appropriate for scaling, such as a single-instance, non-replicated database using a persistent volume claim. In this situation, a deployment strategy of 'recreate' will ensure the pod is restarted after migration, although a brief outage will be experienced.

For more information, refer to the following guide:
https://blog.openshift.com/deploying-highly-available-applications-openshift-kubernetes/

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,
OpenShift SRE
Posted 20 days ago. Nov 27, 2018 - 20:31 UTC
This scheduled maintenance affected: pro-eu-west-1 (Master API Service, Application Creation Service, Docker Registry Service, etcd Service).