Uploaded image for project: 'MicroShift'
  1. MicroShift
  2. USHIFT-1622

rebase does not update kubernetes version within release

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Undefined Undefined
    • openshift-4.14
    • None
    • None
    • None
    • False
    • Hide

      None

      Show
      None
    • False

      Description of problem:

      The rebase script updates the kubernetes version based on the "pod" image dependency, but that dependency is not always updated throughout a release. That means, for example, that while OCP is using 1.27.4 today MicroShift is still on 1.27.1.

      Version-Release number of selected component (if applicable):

      4.14

      How reproducible:

      Always

      Steps to Reproduce:

      1. Look at the k8s.io/kubernetes dependency in go.mod
      2.
      3.
      

      Actual results:

      $ grep k8s.io/kubernetes 
      go.mod	k8s.io/kubernetes v1.27.1

      Expected results:

      The version should be 1.27.1

      Additional info:

      The openshift-apiserver typically updates more often, so we could take the kubernetes dependency from it. This is likely to require special coding in the rebase script because MicroShift does not currently depend on the API server.
      
      We may be able to find another component to use.
      
      We could even investigate just updating to HEAD of openshift/kubernetes directly, although that might be risky if OCP is not also using that same version, so it would be better to track *something* in OCP.

              pmatusza@redhat.com Patryk Matuszak
              dhellman@redhat.com Doug Hellmann
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: