starter-us-east-2a upgrade to OpenShift 3.11.82 is complete, CVE remediation resuming. Estimated completion time to be determined shortly.
Mar 18, 13:00 UTC
starter-us-east-2a is in the process of being upgraded to OpenShift 3.11.82. Due to the intermittent API errors, no estimated completion time is available.
Mar 15, 19:42 UTC
Incident is ongoing and no ETA is available.
Mar 15, 00:47 UTC
OpenShift SRE is aware of a condition affecting some failing routes and periodic API issues and continues to investigate the situation.
Mar 14, 22:10 UTC
We are experiencing a higher rate of errors than initially expected and continue to investigate.
Mar 14, 17:44 UTC
Scheduled maintenance for starter-us-east-2a is still in progress and is taking longer than expected, the current estimate for completion is Mar 15, 2019 at 13:00 UTC.
Mar 14, 12:12 UTC
OSIO clusters need to be patched to finish remediation of https://access.redhat.com/security/cve/cve-2019-5736
SRE is performing maintenance on this cluster.
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:
If you have any questions, please feel free to contact us:
Thank you for choosing Red Hat OpenShift,
Mar 12, 15:48 UTC