Feature Overview (aka. Goal Summary)

Implement an Orchestrator flavor in the RHDH Operator to install the Orchestrator plugins, dependent infrastructure, and configuration, enabling users to immediately start creating and managing workflows in RHDH without manual configuration.

Note: The orchestrator flavor is part of the RHDH Operator flavor concept, which is not fully designed yet and subject to change.

ADR for flavors at https://docs.google.com/document/d/1vIgSutpuPpqpwYRAL54xFgCHpgkJu5RMZbabsQzqEfA/edit?usp=sharing

Goals (aka. expected user outcomes)

• Enable immediate use of workflow orchestration capabilities in RHDH through the Operator.
  • Simplify the installation and configuration of SonataFlow infrastructure.
  • Provide pre-configured orchestrator plugin through the Operator.
  • Reduce time-to-value for workflow orchestration use cases.
• Implement flavor handling in Go code utilizing the kustomize library functionality rather than relying on Helm chart dependencies.

Requirements (aka. Acceptance Criteria):

• Infrastructure Setup:
  • Install required SonataFlow operator and CRDs and Knative.
  • Deploy and configure SonataFlow runtime.
  • Configure network policies and routes as needed.
• RHDH Operator Configuration:

• • Install and configure orchestrator dynamic plugin.
  • Configure required plugin environment variables and secrets.
  • Configure default permissions for workflow management.
• Operator Implementation:

• • Utilize kustomize library functionality for resource management.
  • Make sure existing RHDH installations can be extended with orchestrator plugin with dependencies and infrastructure
  • Implement sensible defaults for the orchestrator flavor.
• Documentation:
  • Document installation process changes (related to Orchestrator) through the Operator.
  • Document resource requirements (CPU, Memory).
  • Document resources required for airgapped environments.
• Testing:
  • Implement tests for the orchestrator flavor in the Operator.

Out of Scope (Optional)

Customer Considerations (Optional)

• The orchestrator flavor currently only works on OpenShift. Support for AKS/EKS/GKE will be added in future versions.
• Customers should be aware that the plugin dependency framework in the Operator is still evolving and subject to change.

Documentation Considerations

• Provide detailed documentation on the installation process using the Operator.
• Document how to select and configure the orchestrator dependencies and infra.
• Include resource requirements and airgapped environment considerations.
• Document any limitations or constraints of the orchestrator flavor.