Uploaded image for project: 'Operator Runtime'
  1. Operator Runtime
  2. OPRUN-3944

[UPSTREAM] Add registry+v1 bundle release attribute #1576

XMLWordPrintable

    • Icon: Epic Epic
    • Resolution: Unresolved
    • Icon: Major Major
    • None
    • None
    • None
    • bundle-release-version
    • In Progress
    • Quality / Stability / Reliability
    • OCPSTRAT-2669TP: native mechanisms to designate override versions for registry+v1 bundles
    • 27% To Do, 0% In Progress, 73% Done
    • False
    • Hide

      None

      Show
      None
    • False
    • Not Selected
    • None
    • 31

      Driving toward immutable bundles and adaptable successor identification, we can introduce a release attribute for bundles. This would allow operator authors to re-release a bundle without affecting catalog metadata which would allow for the selection of highest release attribute for a given bundle version.

      1. write a [brief](https://docs.google.com/document/d/1tX0fXYuflTpTal6z0TbNkrQ7SAkYIKxQj4cPjlFAh4Q/)
      2. write the CSV/FBC RFC
      3. [internal] EP review
      4. implement CSV (add Release version as an optional field in the CSV api#454)
      5. implement FBC (OPRUN-4195,OPRUN-4275,OPRUN-4276: release bundle attribute in version property operator-registry#1792)
      6. add documentation (add bundle release version attribute, substitutes template olm-docs#342)

              rh-ee-jkeister Jordan Keister
              rh-ee-jkeister Jordan Keister
              None
              Xia Zhao Xia Zhao
              None
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated: