3.9.41 minor OpenShift version upgrade for pro-ap-southeast-2
Scheduled Maintenance Report for OpenShift Online Pro
Completed
Upgrade to 3.9.41 is complete.
Posted about 2 months ago. Sep 18, 2018 - 21: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 about 2 months ago. Sep 18, 2018 - 16:16 UTC
Scheduled
The OpenShift Pro cluster, pro-ap-southeast-2, is scheduled to upgrade to version 3.9.41 starting at 16:00 UTC on Sep 18, 2018 and ending at approximately 00:00 UTC on Sep 19, 2018. The upgrade process is engineered to disrupt applications as little as possible, but brief outages may occur during the upgrade. For short periods of time, developers may be unable to create new applications or interact with existing applications. In addition to the OpenShift version upgrade, the following imagestreams will also be updated:

apicast-gateway
dotnet
dotnet-runtime
eap-cd-openshift
fis-java-openshift
fis-karaf-openshift
httpd
java
jboss-amq-62
jboss-amq-63
jboss-datagrid65-client-openshift
jboss-datagrid65-openshift
jboss-datagrid71-client-openshift
jboss-datagrid71-openshift
jboss-datagrid72-openshift
jboss-eap64-openshift
jboss-eap70-openshift
jboss-eap71-openshift
jboss-fuse70-console
jboss-fuse70-eap-openshift
jboss-fuse70-java-openshift
jboss-fuse70-karaf-openshift
jboss-webserver30-tomcat7-openshift
jboss-webserver30-tomcat8-openshift
jboss-webserver31-tomcat7-openshift
jboss-webserver31-tomcat8-openshift
jenkins
mariadb
mongodb
mysql
nodejs
perl
php
postgresql
python
redhat-openjdk18-openshift
redhat-sso72-openshift
redis
rhdm70-decisioncentral-openshift
rhdm70-kieserver-openshift
rhpam70-businesscentral-openshift
rhpam70-kieserver-openshift
ruby
wildfly

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

How does the upgrade work?

During the 3.9 in-place upgrade, existing nodes will be evacuated, which requires pods to be stopped and moved to other nodes in the cluster.

What should you do?

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/
Posted 2 months ago. Sep 05, 2018 - 17:30 UTC
This scheduled maintenance affected: pro-ap-southeast-2 (Master API Service, Application Creation Service, Docker Registry Service, etcd Service).