What is the point of a solid update procedure in OpenShift when it takes you to a buggy version? We want to protect your clusters, and we are getting better at that. The latest iteration of the protection is called Conditional Updates. We provide enough data to evaluate whether the cluster is affected by issues discovered in released versions of OpenShift. If it is, it will warn its administrator and provide more information about the exposure and the risk. The administrator can decide whether they care or want to wait for a version where the problem is fixed. This is an improvement from the previous state, where we would block everyone until the fix is available, including clusters that would be safe. In this talk, I will describe the inner workings of the OpenShift update and how the update recommendation data that drive OpenShift updates are curated, delivered, and evaluated.
As a member of the OpenShift Over-the-Air (OTA) Upgrades team, I am working on the OpenShift components related to upgrades - Cluster Version Operator, Cincinnati and related software.
