Uploaded image for project: 'RH Developer Hub Planning'
  1. RH Developer Hub Planning
  2. RHDHPLAN-179

Merge Orchestrator into RHDH

Prepare for Z ReleasePrepare Test Plan (Y R...XMLWordPrintable

    • 45% To Do, 18% In Progress, 36% Done
    • False
    • Hide

      None

      Show
      None

      Feature Overview (aka. Goal Summary)

      The Orchestrator is a very important feature that customers are looking to use with RHDH. It can be used to provide additional features that are missing from the default Backstage scaffolder. 

      Goals (aka. expected user outcomes)

      The Orchestrator should be available out of the box when a customer is installing RHDH.

       

      Requirements (aka. Acceptance Criteria):

      • As an administrator, when I install RHDH, I want to be able to use RHDH without installing another operator/helm (Merge operators)
      • As an administrator, I should be able to configure where I want to display the Orchestrator plugin. (Bundle the Orchestrator plugin)

      Customer Considerations (Optional)

      Currently, the Orchestrator is using Sonataflow as the backend and only works on OpenShift. Support for AKS/EKS/GKE will be added in a future version. e.g. 1.7 and 1.8

      Documentation Considerations

      Documentation is required to explain how the Orchestrator works, how to use it and how to create a workflow.

              rh-ee-mhild Marcel Hild
              jfargett@redhat.com Christophe Fargette
              Votes:
              0 Vote for this issue
              Watchers:
              14 Start watching this issue

                Created:
                Updated:
                Resolved: