Will there be an impact on the Platform apps?

Prep will involve orphaned image data cleanup and defragmenting the ETCD database. Defragmenting ETCD could cause some latency and slowness but isn't expected to cause any breakage as each pod will be done individually with time to recover between operations. The hard prune will put the registry in read-only mode briefly while the pruner removes any orphaned images.

Upgrade will involve both an upgrade of the core of the cluster as well as draining/reboots of all nodes which will require pods to be drained onto other nodes. There may be some slowness for new pods coming up if it happens that a lot of new pods attempt to start on an empty node (just patched). We will announce daily when work for this will resume and be suspended at the end of each work day.

Emerald upgrade to 4.18

» View Event Details | Created Mon, 15 Jun 2026 16:00:00 +0000

Scheduled

What is happening?

CHG0079162 CITZ - PROD - MCS EMERALD - Pre-upgrade prep work for 4.18

CHG0079163 CITZ - PROD - MCS EMERALD - Upgrade to 4.18

These two changes represent the work involved to upgrade the EMERALD production cluster from Openshift 4.16 to 4.18.

When?

Emerald Prep will run Sunday June 14th 6am to 9am.

Emerald Upgrade will run Monday June 15th to 19th 9am to 5pm each weekday.

Will there be an impact on the Platform apps?

Change CHG0079162 will involve orphaned image data cleanup and defragmenting the ETCD database. Defragmenting ETCD could cause some latency and slowness but isn't expected to cause any breakage as each pod will be done individually with time to recover between operations. The hard prune will put the registry in read-only mode briefly while the pruner removes any orphaned images. Some delays with pod restarts may occur during the ncp upgrade (operator which ties Openshift to NSX).

Change CHG0079163 will involve both an upgrade of the core of the cluster as well as draining/reboots of all nodes which will require pods to be drained onto other nodes. There may be some slowness for new pods coming up if it happens that a lot of new pods attempt to start on an empty node (just patched). We will announce daily when work for this will resume and be suspended at the end of each work day.

Do I need to do anything?

Monitor your applications for disruptions. Well designed applications should be able to tolerate the pod restarts without issue.

Posted: Mon, 15 Jun 2026 09:00:00 +0000

B.C. Government Private Cloud Status Page

Upcoming Events

June 2026

Gold DR upgrade to 4.18