Uploaded image for project: 'OpenShift Kueue'
  1. OpenShift Kueue
  2. OCPKUEUE-303

[Upgrade] - Kueue CR should support upgrades between channels

XMLWordPrintable

    • Icon: Spike Spike
    • Resolution: Unresolved
    • Icon: Undefined Undefined
    • None
    • Kueue 1.1
    • None
    • Node Green Sprint 280

      The goal is to be able to perform an upgrade, between channels, as we currently have working for versions inside the same channel.

       

      Scenario: upgrading from Kueue 1.0.1 to 1.1.0

      When a new version of Kueue is available, costumers should see "Upgrade is available" message under the operator name (in case this update is not being automatically done). 

      The upgrade, despite being in another channel or not, should happen smoothly. 

       

      All testing steps are here, video showing how to reproduce here.

       

      Possible solutions: in this slack thread, it was suggested to add a "replaces: kueue-operator.v1.0.1" under kueue-operator.v1.1.0 entry. This solution partially works. When we select the channel with the version to be upgraded, a message saying "Upgrade is available" is shown and upgrade process starts. However, kueue-controller pods keep restarting.

      Pod logs and crio (couldn't set the logLevel to debug) logs were saved.

       

              rh-ee-pbhojara Pannaga Rao Bhoja Ramamanohara
              rh-ee-anahas Alice Nahas
              None
              None
              None
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated: