Scheduled -
The OpenShift Pro cluster, pro-ap-southeast-2, is scheduled to upgrade starting at 16:00 UTC on Nov 12, 2018 and ending at approximately 00:00 UTC on Nov 13, 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
java
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-webserver30-tomcat7-openshift
jboss-webserver30-tomcat8-openshift
jboss-webserver31-tomcat7-openshift
jboss-webserver31-tomcat8-openshift
nodejs
perl
php
python
redhat-openjdk18-openshift
redhat-sso72-openshift
ruby
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.
Oct 29, 20:05 UTC