The pro-ap-southeast-2 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:
To disable automatic upgrade of these applications, modify the imageChangeTrigger in the application's DeployConfig or BuildConfig.
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:
If you have any questions, please feel free to contact us:
Thank you for choosing Red Hat OpenShift,