Uploaded image for project: 'OpenShift Pipelines'
  1. OpenShift Pipelines
  2. SRVKP-3110

CI: create a cronjob checking index image upgrade paths

XMLWordPrintable

    • Icon: Story Story
    • Resolution: Unresolved
    • Icon: Normal Normal
    • None
    • None
    • p12n, QA
    • Pipelines Sprint 243, Pipelines Sprint 244, Pipelines Sprint 246

      Story (Required)

      Implement a cronjob on CI that would regularly check upgrade paths in production index images such as

      • registry.redhat.io/redhat/redhat-operator-index:v4.11
      • registry.redhat.io/redhat/redhat-operator-index:v4.12
      • registry.redhat.io/redhat/redhat-operator-index:v4.13

      Background (Required)

      Release 1.10.1 was not available on OpenShift 4.12. We verified it in stage, everything was fine but then something broke and customers were able to update to 1.10.1 on OpenShift 1.11 and 1.13 (not released yet at that time) but it was not availabe on 1.12.

      We would have noticed that before our customers did if we ran e2e tests after release or if we checked metadata in index image after release.

      Out of scope

      Approach (Required)

      Download current version of production catalog source index image and check available versions of OpenShift Pipelines operator.

      Alternatively we could run acceptance-tests shortly after release on all versions of OpenShift but that would be much slower, costlier and unstable.

              Unassigned Unassigned
              ppitonak Pavol Pitoňák
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated: