security remediation for pro-ap-southeast-2
Scheduled Maintenance Report for OpenShift Online Pro
Completed
The security remediation for pro-ap-southeast-2 has been successfully completed.
Posted 2 months ago. May 15, 2019 - 19:02 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 2 months ago. May 15, 2019 - 17:01 UTC
Scheduled
SRE is performing security remediation on pro-ap-southeast-2.

Cluster compute nodes are part of an AWS scale group. A new scale group will be created that includes the latest, remediated AMI. This new scale group will be activated and when all the instances are up and available, the legacy nodes will be marked not schedulable, and the new instances marked schedulable. This action will move all compute workloads to the newly created and remediated instances. Once all the workloads are migrated, the legacy scale group and associated instances will be decommissioned.

What should you do?
You can minimize the impact on your applications by scaling your services to more than one 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. May 15, 2019 - 15:54 UTC
This scheduled maintenance affected: pro-ap-southeast-2 (Master API Service, Application Creation Service, Docker Registry Service, etcd Service).