[release-1.9] fix: switch Orchestrator plugins to OCI [RHDHBUGS-2527]

[rm3l]

Manual cherry-pick of #307

Fixes RHDHBUGS-2527

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[rhdh-qodo-merge]

PR Reviewer Guide 🔍

Here are some key observations to aid the review process:

🎫 Ticket compliance analysis 🔶 RHDHBUGS-2527 - Partially compliant Compliant requirements: Update the Helm chart Orchestrator plugin configuration (values/docs) accordingly. (Potentially) switch Orchestrator plugins to OCI-based artifacts instead of NPM tarballs. Non-compliant requirements: Fix RHDH 1.9 startup/readiness failure when deploying with Orchestrator enabled via Helm or Operator. Ensure Orchestrator plugin artifacts/versions are compatible with the Backstage version used in RHDH 1.9. Requires further human verification: Validate the deployment starts successfully (readiness probe passes) with Orchestrator enabled.

⏱️ Estimated effort to review: 2 🔵🔵⚪⚪⚪

🔒 No security concerns identified

⚡ Recommended focus areas for review Templating Risk The OCI references rely on {{inherit}} being passed through Helm templating as a literal for downstream processing. Verify quoting/escaping is correct across Helm rendering and any plugin installer that consumes this value; mis-rendering could produce invalid image references and break plugin fetching. - package: 'oci://registry.access.redhat.com/rhdh/red-hat-developer-hub-backstage-plugin-orchestrator-backend:{{ "{{inherit}}" }}' disabled: false - package: 'oci://registry.access.redhat.com/rhdh/red-hat-developer-hub-backstage-plugin-orchestrator-form-widgets:{{ "{{inherit}}" }}' disabled: false - package: 'oci://registry.access.redhat.com/rhdh/red-hat-developer-hub-backstage-plugin-orchestrator:{{ "{{inherit}}" }}' disabled: false - package: 'oci://registry.access.redhat.com/rhdh/red-hat-developer-hub-backstage-plugin-scaffolder-backend-module-orchestrator:{{ "{{inherit}}" }}' disabled: false

📚 Focus areas based on broader codebase context Missing Config The new OCI-based orchestrator.plugins entries no longer include pluginConfig (notably orchestrator.dataIndexService.url) that was previously embedded in the chart values. Validate that this configuration is still provided elsewhere (e.g., via appConfig or another values block), otherwise the orchestrator backend/scaffolder modules may start without the required Data Index endpoint configuration. (Ref 1, Ref 2) - package: 'oci://registry.access.redhat.com/rhdh/red-hat-developer-hub-backstage-plugin-orchestrator-backend:{{ "{{inherit}}" }}' disabled: false - package: 'oci://registry.access.redhat.com/rhdh/red-hat-developer-hub-backstage-plugin-orchestrator-form-widgets:{{ "{{inherit}}" }}' disabled: false - package: 'oci://registry.access.redhat.com/rhdh/red-hat-developer-hub-backstage-plugin-orchestrator:{{ "{{inherit}}" }}' disabled: false - package: 'oci://registry.access.redhat.com/rhdh/red-hat-developer-hub-backstage-plugin-scaffolder-backend-module-orchestrator:{{ "{{inherit}}" }}' disabled: false Reference reasoning: The reference dynamic plugin configurations for the orchestrator backend/scaffolder components explicitly set pluginConfig.orchestrator.dataIndexService.url, indicating this is expected to be supplied alongside the package. Switching only the package to OCI without preserving the config deviates from that established configuration pattern and risks losing required runtime settings.

📄 References redhat-developer/rhdh/dynamic-plugins.default.yaml [1388-1408] redhat-developer/rhdh/dynamic-plugins.default.yaml [1346-1351] redhat-developer/rhdh/dynamic-plugins.default.yaml [1352-1359] redhat-developer/rhdh-operator/dist/rhdh/install.yaml [2206-2215] redhat-developer/rhdh-operator/examples/orchestrator.yaml [1-22] redhat-developer/rhdh/default.packages.yaml [77-87] redhat-developer/rhdh-chart/charts/backstage/ci/with-orchestrator-values.yaml [1-21] redhat-developer/rhdh-chart/charts/backstage/ci/with-orchestrator-and-dynamic-plugins-npmrc-values.yaml [1-24]

[rhdh-qodo-merge]

PR Type

Enhancement

---

Description

• Switch orchestrator plugins from NPM to OCI artifact registry

• Simplify plugin configuration by removing explicit versions and integrity hashes

• Leverage {{inherit}} option to inherit versions from dynamic-plugins catalog

• Bump Helm chart version from 5.0.2 to 5.0.3

---

File Walkthrough

	Relevant files
Configuration changes	Chart.yaml Bump chart version to 5.0.3                                                            charts/backstage/Chart.yaml Increment chart version from 5.0.2 to 5.0.3 +1/-1
Documentation	README.md Update documentation with new chart version                            charts/backstage/README.md Update version badge from 5.0.2 to 5.0.3 Update helm install command example to use new chart version +3/-3
Enhancement	values.yaml Migrate orchestrator plugins to OCI registry                          charts/backstage/values.yaml Replace 4 NPM-based orchestrator plugins with 4 OCI-based plugins from registry.access.redhat.com Remove explicit package integrity hashes and version pinning Remove detailed pluginConfig sections for backend and frontend plugins Simplify configuration to use {{inherit}} for automatic version inheritance from catalog +8/-53

---

[rm3l]

Merging as a manual cherry-pick of #307

/lgtm

[openshift-ci]

@rm3l: you cannot LGTM your own PR.

Details

In response to this:

Merging as a manual cherry-pick of #307

/lgtm

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[rhdh-qodo-merge]

PR Code Suggestions ✨

Explore these optional code suggestions:

Category	Suggestion	Impact
Possible issue	Restore missing plugin configurations Restore the pluginConfig sections for the orchestrator plugins, as their removal will likely break functionality by leaving backend and frontend components unconfigured. charts/backstage/values.yaml [397-404] - package: 'oci://registry.access.redhat.com/rhdh/red-hat-developer-hub-backstage-plugin-orchestrator-backend:{{ "{{inherit}}" }}' disabled: false + pluginConfig: + orchestrator: + dataIndexService: + url: http://sonataflow-platform-data-index-service.{{ .Release.Namespace }} - package: 'oci://registry.access.redhat.com/rhdh/red-hat-developer-hub-backstage-plugin-orchestrator-form-widgets:{{ "{{inherit}}" }}' disabled: false + pluginConfig: + dynamicPlugins: + frontend: + red-hat-developer-hub.backstage-plugin-orchestrator-form-widgets: {} - package: 'oci://registry.access.redhat.com/rhdh/red-hat-developer-hub-backstage-plugin-orchestrator:{{ "{{inherit}}" }}' disabled: false + pluginConfig: + dynamicPlugins: + frontend: + red-hat-developer-hub.backstage-plugin-orchestrator: + appIcons: + - name: orchestratorIcon + importName: OrchestratorIcon + dynamicRoutes: + - path: /orchestrator + importName: OrchestratorPage + menuItem: + icon: orchestratorIcon + text: Orchestrator + entityTabs: + - path: /workflows + title: Workflows + mountPoint: entity.page.workflows + mountPoints: + - mountPoint: entity.page.workflows/cards + importName: OrchestratorCatalogTab + config: + layout: + gridColumn: "1 / -1" + if: + anyOf: + - IsOrchestratorCatalogTabAvailable - package: 'oci://registry.access.redhat.com/rhdh/red-hat-developer-hub-backstage-plugin-scaffolder-backend-module-orchestrator:{{ "{{inherit}}" }}' disabled: false + pluginConfig: + orchestrator: + dataIndexService: + url: http://sonataflow-platform-data-index-service.{{ .Release.Namespace }} Apply / Chat Suggestion importance[1-10]: 9 __ Why: The suggestion correctly identifies that removing the pluginConfig is a high-risk change that could break orchestrator functionality, as this configuration seems essential for backend and frontend plugins to work correctly.	High
More