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

Support Federation on OSD and ARO

    XMLWordPrintable

Details

    • Story
    • Resolution: Done
    • Major
    • None
    • None
    • None

    Description

      We currently document that Federation is not supported on OSD, ARO and ROSA*. This issue is to identify what steps we would need to take to extend support for federation across OpenShift deployed on these platforms. Once that's done, we can remove this from the limitations section in our federation documentation.

      • We haven't yet announced official support for Service Mesh on ROSA, though it's not expected to require substantial hurdles. When we do announce support for Service Mesh on ROSA, it should include federation as well.
      • Priority (based on requests to date) should be for ARO.

      Attachments

        Issue Links

          is documented by

          Epic - Created by Jira Software - do not edit or delete. Issue type for a big user story that needs to be broken down. OSSM-2527 Support Service Mesh 2.0 on OSD

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Epic - Created by Jira Software - do not edit or delete. Issue type for a big user story that needs to be broken down. OSSM-2528 ROSA docs

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Task - Represents a small unit of work that is not end-user facing. OSSM-2883 Publish service mesh docs to ROSA

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Task - Represents a small unit of work that is not end-user facing. OSSM-3083 Publish service mesh docs to OpenShift Dedicated

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed
          is related to

          Sub-task - The sub-task of the issue OSSM-1685 QE: Regression testing on ARO - Federation, Single Cluster

          • Undefined - Priority not specified.
          • Closed

          Sub-task - The sub-task of the issue OSSM-1686 QE: Regression testing on ARO - Federation, Multiple Clusters

          • Undefined - Priority not specified.
          • Closed

          Sub-task - The sub-task of the issue OSSM-1687 QE: Regression testing on ARO - Federation, Failover

          • Undefined - Priority not specified.
          • Closed

          Activity

            People

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

              Dates

                Created:
                Updated:
                Resolved: