Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix(openshift): drop z from next calculated y-stream #2324

Merged

Commits on Aug 12, 2021

  1. fix(openshift): drop z from next calculated y-stream

    When determining operator compatibility, drop z and build
    versions in the calculation of the next Y-stream (minor)
    release of OpenShift.
    
    e.g. If the current version is v4.9.5+build, the next Y-stream is
    calculated as v4.10.0.
    
    If a pre-release is included, drop it as well but don't increment
    the minor version.
    
    e.g. If the current version is v4.10.0-rc, the next Y-stream is
    calculated as v4.10.0.
    
    Before this change, the next Y-stream was the result of simply
    iterating the cluster's minor version. When the cluster was at
    a patch version greater than that specified by an operator, upgrades
    would be erroneously blocked.
    
    e.g. If the current version was v4.9.5, the next version would be
    calculated as v4.10.5, which would block upgrades on operators with
    max versions set to v4.10 -- or more explicitly [v4.10.0, v4.10.5) (')'
    is read "exclusive").
    
    Signed-off-by: Nick Hale <njohnhale@gmail.com>
    njhale committed Aug 12, 2021
    Configuration menu
    Copy the full SHA
    bf11c93 View commit details
    Browse the repository at this point in the history