Blog on RHDH Orchestrator

Customer Q&A: Common Questions About Orchestrator

Wed, 06 Aug 2025 00:00:00 +0000

Customer Q&A: Common Questions About Orchestrator

This document will serve as the Orchestrator’s Q&A collection. Customer submitted questions are provided along with detailed answers.

Getting Started & Overview
Development & Testing
Building & Deployment
Authentication & Security
Integration & APIs
UI & User Experience
Subflows
Architecture & Infrastructure
Advanced Topics & Troubleshooting

Getting Started & Overview

Q: How mature is the solution Orchestrator? Is it still cutting edge technology or already used by other customers?

A: The Orchestrator was GAed in RHDH 1.5. The current version is 1.6 and it will be merged into RHDH in 1.7. At this point we will have one unified operator which supports RHDH and the Orchestrator facilities. There are other customers using the Orchestrator in production - even on a large scale with multiple thousands of users and others are onboarding to it currently.

Upgrading from Orchestrator 1.6 to RHDH 1.7

Thu, 18 Sep 2025 00:00:00 +0000

Upgrading from Orchestrator 1.6 to RHDH 1.7

Starting with Red Hat Developer Hub (RHDH) v1.7, Orchestrator will be shipped as an integrated component of RHDH, available through both the RHDH operator and RHDH Helm Chart. Users currently running Orchestrator v1.6 cannot directly upgrade to “Orchestrator 1.7”. Instead, they must install the new RHDH release with Orchestrator enabled and migrate their existing data and resources.

Background: RHDH and Orchestrator Integration

From RHDH v1.7 onwards, Orchestrator will be shipped alongside RHDH as a plugin with all current capabilities. The components will be installed together, and Orchestrator will no longer have its own dedicated operator. For detailed information about this transition, see our blog post about installing Orchestrator via RHDH Chart.

Hacking The Build and Deployment Process of Serverless Workflows

Mon, 28 Apr 2025 00:00:00 +0000

Hacking The Build and Deployment Process of Serverless Workflows

In this guide, we’ll dive under the hood of the serverless workflow build process, examine how it works internally, and learn how to take control of it when needed.

The Problem

We’re working with a repository that contains an issue with the standard workflow build script described in our previous post.

Prerequisites

Have kn-workflow CLI installed from official link with version >= v1.36.
Have a kafka cluster running on an OCP cluster
Have RHDH and the orchestrator installed

Generating Manifests with the kn-workflow CLI

The kn-workflow CLI serves multiple purposes in development, testing, and deployment. For our needs, we’ll use it solely to generate Kubernetes manifests.

Installing Orchestrator via the Red Hat Developer Hub Helm Chart

Mon, 28 Apr 2025 00:00:00 +0000

Installing Orchestrator via the Red Hat Developer Hub Helm Chart

This blog introduces a streamlined installation method that allows users to deploy Orchestrator alongside Red Hat Developer Hub (RHDH) using a Helm Chart and with minimal configuration and effort.

With this approach, the Orchestrator Plugins are installed directly within RHDH and deployed to a single target namespace. As a result, all RHDH components, Openshift Serverless Logic platform services, and serverless workflows coexist within the same namespace, simplifying the deployment footprint and operational model.

Building and Deploying Serverless Workflows

Mon, 21 Apr 2025 00:00:00 +0000

The Orchestrator provides a way to run workflows directly from Backstage/RHDH. But how do these workflows actually become available in Backstage?
This blog will take you through the journey from running a workflow locally on your machine to having it deployed on a cluster and available in the Orchestrator plugin.

Note: This blog focuses on the build and deploy process, not workflow development itself. If you’re looking for workflow development resources, there are guides available online.

Creating Extracted OpenAPI Documents for Integrating Systems on Serverless Workflows

Thu, 05 Sep 2024 00:00:00 +0000

Creating Extracted OpenAPI Documents for Integrating Systems on Serverless Workflows

The blog post will guide developers on how to extract openAPI documents to a new file of manageable size. The need for this procedure has risen in account of restrictions that Quarkus imposes with accepting large YAML files as input (see appendix). This restriction directs us to be mindful and plan ahead which resources services we would need in our workflow.

Production Mode vs. Dev Mode

Sun, 30 Jun 2024 00:00:00 +0000

When setting up workflow orchestration, it’s crucial to understand the differences between production mode and development (dev) mode, particularly in terms of infrastructure requirements. This distinction ensures that workflows are efficiently managed and executed based on their intended use case. Here, we’ll explore these differences, focusing on the infrastructure required to run workflows in each mode.

Production Mode

Production mode is tailored for environments where stability, reliability, and scalability are paramount. The Orchestrator Helm chart or Orchestrator operator is designed specifically to meet the demanding requirements of production environments. Key requirements include:

Serverless Workflows: an Automated Developer Experience

Fri, 15 Mar 2024 00:00:00 +0000

Great job on installing the Orchestrator plugin and the SonataFlow operator! But what comes next?

If you aim to understand the full development lifecycle of serverless workflows, from zero to production, then you’ve come to the right place.

Thanks to the Orchestrator functions and automations, developers can now focus solely on building their applications without being burdened by unnecessary cognitive load. Let’s delve into how to effectively manage the end-to-end software development lifecycle of serverless workflows, leveraging these built-in capabilities.

Serverless Workflows: an Automated Developer Experience Step-by-Step

Fri, 15 Mar 2024 00:00:00 +0000

In this blog, we’ll guide you through the journey from a software template to bootstrapping the workflow development, building, packaging, releasing, and deploying it on a cluster. If you need a high-level explanation or want to dive into the architecture of the solution, check out our previous blog. You can also watch a detailed demonstration of the content covered in this post in this recording.

Prerequisites and Assumptions

This blog assumes familiarity with specific tools, technologies, and methodologies. We’ll start with RHDH (Backstage) by launching a basic workflow template, working with GitHub for source control, pushing the workflow image to Quay, and using Kustomize to deploy the ArgoCD application for GitOps.

What is Sonataflow Operator?

Mon, 19 Feb 2024 00:00:00 +0000

SonataFlow Operator

The SonataFlow Operator defines a set of Kubernetes Custom Resources to help users to deploy SonataFlow projects on Kubernetes and OpenShift.

Please visit our official documentation to know more.

Available modules for integrations

If you’re a developer, and you are interested in integrating your project or application with the SonataFlow Operator ecosystem, this repository provides a few Go Modules described below.

SonataFlow Operator Types (api)

Every custom resource managed by the operator is exported in the module api. You can use it to programmatically create any custom type managed by the operator. To use it, simply run:

Blog on RHDH Orchestrator

Customer Q&A: Common Questions About Orchestrator

Customer Q&A: Common Questions About Orchestrator

Table of Contents

Getting Started & Overview

Upgrading from Orchestrator 1.6 to RHDH 1.7

Upgrading from Orchestrator 1.6 to RHDH 1.7

Background: RHDH and Orchestrator Integration

Hacking The Build and Deployment Process of Serverless Workflows

Hacking The Build and Deployment Process of Serverless Workflows

The Problem

Prerequisites

Generating Manifests with the kn-workflow CLI

Installing Orchestrator via the Red Hat Developer Hub Helm Chart

Installing Orchestrator via the Red Hat Developer Hub Helm Chart

Building and Deploying Serverless Workflows

Creating Extracted OpenAPI Documents for Integrating Systems on Serverless Workflows

Creating Extracted OpenAPI Documents for Integrating Systems on Serverless Workflows

Production Mode vs. Dev Mode

Production Mode

Serverless Workflows: an Automated Developer Experience

Serverless Workflows: an Automated Developer Experience Step-by-Step

Prerequisites and Assumptions

What is Sonataflow Operator?

SonataFlow Operator

Available modules for integrations

SonataFlow Operator Types (api)