Uploaded image for project: 'OpenShift Storage'
  1. OpenShift Storage
  2. STOR-2216

Early chore: update OCP version in OLM metadata

This issue is archived. You can view it, but you can't modify it. Learn more

XMLWordPrintable

    • Icon: Story Story
    • Resolution: Unresolved
    • Icon: Undefined Undefined
    • None
    • None
    • None

      Update OCP release number in OLM metadata manifests of:

      • local-storage-operator
      • aws-efs-csi-driver-operator
      • gcp-filestore-csi-driver-operator
      • secrets-store-csi-driver-operator
      • smb-csi-driver-operator

      OLM metadata of the operators are typically in /config/manifest directory of each operator. Example of such a bump: https://github.com/openshift/aws-efs-csi-driver-operator/pull/56 

      We should do it early in the release, so QE can identify new operator builds easily and they are not mixed with the old release.

              jdobson@redhat.com Jonathan Dobson
              rhn-engineering-jsafrane Jan Safranek
              Archiver:
              rhn-engineering-jsafrane Jan Safranek

                Created:
                Updated:
                Resolved:
                Archived: