» Published on
The migration to OVN is now complete.
Previously reported connectivity issues between pods have all been resolved.
» UpdatedPod connectivity issues on SILVER cluster - April 29 2026
We’ve had reports from one team regarding communication problems pods between pods in the SILVER cluster
The potential impact timeline is from the beginning of recent OVN Migration work in the SILVER cluster from April 20, though we first received the report of a problem on April 28.
We’re currently aware of this impacting a small number of pods, and have escalated to the Vendor (Red Hat).
We are interested to hear from teams who’ve noticed something similar in their namespaces. Please reply to the thread in #devops-operations https://chat.developer.gov.bc.ca/channel/devops-operations to report what you’ve noticed.
» UpdatedThis change is now in progress
» UpdatedThe current Container Network Interface (CNI) called OpenShift SDN is deprecated and not available in the next version of OpenShift. We need to move to OVNKubernetes CNI to unlock the upgrade path to OpenShift 4.18.
The upgrade requires a rolling restart of all nodes in the cluster twice. API nodes and Infra nodes are highly available and will fail over services as needed.
As the node drains are managed by OpenShift operator automation, Platform Ops has no way to control the speed of drains.
We may continue to see slow or delayed storage operations like mounting PVCs to pods. Pods drained from one node onto another node may see up to 45 min delay until it starts. The best solution is to have multiple replicas so that a single pod failing to start does not cause application downtime.
» Updated