Uploaded image for project: 'Knative Serving'
  1. Knative Serving
  2. SRVKS-371

Ensure OCP 4.1 clusters stay on 1.2.0, OCP 4.2+ clusters get 1.3.0

XMLWordPrintable

    • Icon: Story Story
    • Resolution: Done
    • Icon: Major Major
    • 1.3.0
    • None
    • None
    • Serverless Sprint 176, Serverless Sprint 177

      We need to ensure that once we release 1.3.0 (Serving 0.10), it only goes out to OpenShift 4.2 or higher clusters. There's a minKubeVersion we can set in ClusterServiceVersion files that may accomplish this. I don't know if that's all we need or if there's something else.

      The expected outcome is that once we release 1.3.0, OpenShift 4.1 clusters continue to work on Serverless 1.2.0 without being upgraded to 1.3.0. OpenShift 4.2 clusters should get upgraded from Serverless 1.2.0 to 1.3.0.

            [SRVKS-371] Ensure OCP 4.1 clusters stay on 1.2.0, OCP 4.2+ clusters get 1.3.0

            Ashleigh Brennan added a comment -

            I'm not sure there's a need to mention this in release notes since the 1.3.0 release notes will only be in OCP 4.2? 1.2.0 will remain for 4.1.

            Ashleigh Brennan added a comment - I'm not sure there's a need to mention this in release notes since the 1.3.0 release notes will only be in OCP 4.2? 1.2.0 will remain for 4.1.

            Jim Crossley added a comment -

            Fixed by https://github.com/openshift-knative/serverless-operator/pull/56

            Jim Crossley added a comment - Fixed by https://github.com/openshift-knative/serverless-operator/pull/56

              jcrossle@redhat.com Jim Crossley
              bbrownin@redhat.com Ben Browning
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: