-
Story
-
Resolution: Unresolved
-
Major
-
None
-
None
-
None
-
Product / Portfolio Work
-
False
-
-
False
-
None
-
None
-
None
-
None
We need to be able to differentiate Major version upgrades from Minor in the variant registry. We should agree on a naming standard and include matching within https://github.com/openshift/sippy/blob/f7ef70002acafd7874c0e8eb5f1219629db0568e/pkg/variantregistry/ocp.go#L605-L615.
Preferably since we are starting new here we should enforce the use of major in the naming to drive the variant value, like (-\d+\.\d+-.*-.*-\d+\.\d+-major)
As a fallback we could evaluate the VariantReleaseMajor and VariantFromReleaseMajor as well.
A stretch goal is to review ClusterData and consider setting the Upgrade variant within CalculateVariantsForJob