You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This commit introduces OLM support for fail forward upgrades. Existing
upgrade behavior is now defined as "Default" upgrade behavior. A new
upgrade strategy referred to as UnsafeFailForward has been introduced
in a tech preview state. When fail forward upgrades are enabled, CSVs
will now be able to move from the failed state to the replacing state,
effectively allowing operators in a namespace to fail forward from
failed installs or upgrades. Additionally, it will be possible to
recover from failed installPlans by updating the upgrade graph defined
in the catalog. Fail forward upgrades are generally unsafe and
unsupported as they could result in unexpected behavior or lost data
due to the fact that critical version of an operator may not be
visited.
Signed-off-by: Alexander Greene <[email protected]>
syncError=fmt.Errorf("fail forward upgrades enabled, unable to identify last CSV in replacement chain")
2117
+
return
2118
+
}
2119
+
2120
+
next=lastCSVInChain
2121
+
}
2122
+
ifnext!=nil {
2091
2123
ifnext.Status.Phase==v1alpha1.CSVPhaseSucceeded {
2092
2124
out.SetPhaseWithEvent(v1alpha1.CSVPhaseDeleting, v1alpha1.CSVReasonReplaced, "has been replaced by a newer ClusterServiceVersion that has successfully installed.", now, a.recorder)
0 commit comments