Uploaded image for project: 'OpenShift Service Mesh'
  1. OpenShift Service Mesh
  2. OSSM-8043

OSSM 3 "Understanding Versioning" section

XMLWordPrintable

    • Icon: Story Story
    • Resolution: Obsolete
    • Icon: Critical Critical
    • None
    • None
    • Sail Operator
    • False
    • Hide

      None

      Show
      None
    • False

      This is perhaps a sub-topic under "upgrading", and is to document the OSSM 3 equivalent information that is provided here: https://docs.openshift.com/container-platform/4.16/service_mesh/v2x/upgrading-ossm.html#ossm-versioning_ossm-upgrade. It will be different in OSSM 3 vs 2.

      Background: OSSM's versioning schema is different than most operators. Most operators have a single version for both the operator and operand, thus when we talk about version 1.2.3, it means the same thing across the lifecycle page, the operator installation page and for the operand (application) under management. Many users assume OSSM follows a similar pattern, but it does not...and that can be confusing. We are also changing our approach from OSSM 2.

      Related document on OSSM 3 versioning: https://docs.google.com/document/d/1LKGTJ0DjIL6XWhqHumUq8XmQEpu9CqtuOl1KrP9xT_k/edit

      More details TBD...

              Unassigned Unassigned
              jlongmui@redhat.com Jamie Longmuir
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: