Monitoring - The fuse-ignite cluster is undergoing an upgrade.

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 upgrade, applications using the following imagestreams will be automatically updated:

apicast-gateway
dotnet
dotnet-runtime
fis-java-openshift
fis-karaf-openshift
httpd
jboss-amq-63
jboss-datagrid71-client-openshift
jboss-datagrid71-openshift
jboss-eap70-openshift
jboss-eap71-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
redis
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.7/dev_guide/deployments/basic_deployment_operations.html#image-change-trigger

How does the upgrade work?

During the 3.7 in-place upgrade, existing nodes will be evacuated, which requires pods to be stopped and moved to other nodes in the cluster (including any temporary nodes).

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/
Apr 19, 15:21 UTC
Investigating - We're experiencing capacity issues on the cluster, and are actively working on the solution.

Thank you for using OpenShift
Apr 11, 13:17 UTC
starter-us-east-1 Operational
90 days ago
100.0 % uptime
Today
Master API Service   Operational
90 days ago
100.0 % uptime
Today
Application Creation Service   Operational
90 days ago
100.0 % uptime
Today
Docker Registry Service   Operational
90 days ago
100.0 % uptime
Today
etcd Service   Operational
90 days ago
100.0 % uptime
Today
starter-us-east-2 Operational
90 days ago
100.0 % uptime
Today
Master API Service   Operational
90 days ago
100.0 % uptime
Today
Application Creation Service   Operational
90 days ago
100.0 % uptime
Today
Docker Registry Service   Operational
90 days ago
100.0 % uptime
Today
etcd Service   Operational
90 days ago
100.0 % uptime
Today
starter-us-west-2 Operational
90 days ago
100.0 % uptime
Today
Master API Service   Operational
90 days ago
100.0 % uptime
Today
Application Creation Service   Operational
90 days ago
100.0 % uptime
Today
Docker Registry Service   Operational
90 days ago
100.0 % uptime
Today
etcd Service   Operational
90 days ago
100.0 % uptime
Today
starter-us-west-1 Operational
90 days ago
100.0 % uptime
Today
etcd Service   Operational
90 days ago
100.0 % uptime
Today
Application Creation Service   Operational
90 days ago
100.0 % uptime
Today
Master API Service   Operational
90 days ago
100.0 % uptime
Today
Docker Registry Service   Operational
90 days ago
100.0 % uptime
Today
starter-ca-central-1 Operational
90 days ago
100.0 % uptime
Today
etcd Service   Operational
90 days ago
100.0 % uptime
Today
Application Creation Service   Operational
90 days ago
100.0 % uptime
Today
Master API Service   Operational
90 days ago
100.0 % uptime
Today
Docker Registry Service   Operational
90 days ago
100.0 % uptime
Today
starter-us-east-2a Operational
90 days ago
100.0 % uptime
Today
Master API Service   Operational
90 days ago
100.0 % uptime
Today
Application Creation Service   Operational
90 days ago
100.0 % uptime
Today
etcd Service   Operational
90 days ago
100.0 % uptime
Today
Docker Registry Service   Operational
90 days ago
100.0 % uptime
Today
fuse-ignite Under Maintenance
90 days ago
100.0 % uptime
Today
Master API Service   Under Maintenance
90 days ago
100.0 % uptime
Today
Application Creation Service   Under Maintenance
Docker Registry Service   Under Maintenance
etcd Service   Under Maintenance
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Past Incidents
Apr 20, 2018

No incidents reported today.

Apr 19, 2018
Resolved - This incident has been resolved.
Apr 19, 06:48 UTC
Investigating - We're experiencing route issues and service name resolution on the cluster, and are actively working on the solution.Thank you for using OpenShift
Apr 18, 08:07 UTC
Apr 17, 2018

No incidents reported.

Apr 16, 2018

No incidents reported.

Apr 15, 2018

No incidents reported.

Apr 14, 2018

No incidents reported.

Apr 13, 2018

No incidents reported.

Apr 12, 2018

No incidents reported.

Apr 11, 2018
Resolved - This incident has been resolved.
Apr 11, 01:55 UTC
Monitoring - The OpenShift Online Starter environment is undergoing an upgrade. No application downtime is expected.
Apr 10, 13:38 UTC
Apr 10, 2018
Resolved - This incident has been resolved.
Apr 10, 13:38 UTC
Monitoring - The OpenShift Online Starter environment is undergoing an upgrade. No application downtime is expected.
Apr 9, 13:23 UTC
Apr 8, 2018

No incidents reported.

Apr 7, 2018

No incidents reported.

Apr 6, 2018
Resolved - This incident has been resolved.
Apr 6, 18:40 UTC
Monitoring - The OpenShift Online Starter environment is undergoing an upgrade. No application downtime is expected.
Mar 26, 13:07 UTC
Resolved - This incident has been resolved.
Apr 6, 18:39 UTC
Monitoring - The OpenShift Online Starter environment is undergoing an upgrade. No application downtime is expected.
Mar 27, 16:41 UTC