Skip to content

RHDHBUGS-2625: Add procedure to configure Orchestrator to connect to existing PostgreSQL infrastructure#2199

Open
jmagak wants to merge 9 commits into
redhat-developer:mainfrom
jmagak:RHDHBUGS-2625-Add-section-how-to-disable-SonataFlow-references-for-Orchestrator-plugins-managed-by-Operator
Open

RHDHBUGS-2625: Add procedure to configure Orchestrator to connect to existing PostgreSQL infrastructure#2199
jmagak wants to merge 9 commits into
redhat-developer:mainfrom
jmagak:RHDHBUGS-2625-Add-section-how-to-disable-SonataFlow-references-for-Orchestrator-plugins-managed-by-Operator

Conversation

@jmagak
Copy link
Copy Markdown
Member

@jmagak jmagak commented May 15, 2026

…gins

IMPORTANT: Do Not Merge - To be merged by Docs Team Only

Version(s): 1.8, 1.9, 1.10, main

Issue: RHDHBUGS-2625

Preview:

5.2. Configure Orchestrator to connect to existing PostgreSQL infrastructure

@rhdh-bot
Copy link
Copy Markdown
Collaborator

rhdh-bot commented May 15, 2026

PR Build Results

Build passed -- 34/34 titles | 71s
Preview: https://redhat-developer.github.io/red-hat-developers-documentation-rhdh/pr-2199/


Content Quality Assessment

CQA Report

  • CQA-00a: Orphaned modules
  • CQA-00b: Directory structure
  • CQA-01: Vale AsciiDoc DITA compliance
  • CQA-02: Verify assembly structure
  • CQA-03: Verify content type metadata
  • CQA-04: Verify module templates
  • CQA-05: Verify required modular elements
  • CQA-06: Verify assemblies follow official template (one user story)
  • CQA-07: Verify TOC depth (max 3 levels)
  • CQA-08: Verify short description content quality
  • CQA-09: Verify short description format
  • CQA-10: Verify titles are brief, complete, and descriptive
  • CQA-11: Verify procedure prerequisites
  • CQA-12: Verify grammar and style (Vale)
  • CQA-13: Verify content matches declared type
  • CQA-14: Verify no broken links
  • CQA-15: Check redirects
  • CQA-16: Verify official product names
  • CQA-17: Verify legal disclaimers for preview features

Summary

Checks: 19 total, 19 pass, 0 fail

19 checks: 19 pass, 0 fail

Run node build/scripts/cqa/index.js --all --fix locally to review and auto-fix issues.


Updated 2026-05-19 05:16:31 UTC

@jmagak jmagak force-pushed the RHDHBUGS-2625-Add-section-how-to-disable-SonataFlow-references-for-Orchestrator-plugins-managed-by-Operator branch from abcd177 to 26474f9 Compare May 15, 2026 12:52
@jmagak jmagak force-pushed the RHDHBUGS-2625-Add-section-how-to-disable-SonataFlow-references-for-Orchestrator-plugins-managed-by-Operator branch from 1ddeeb7 to f91ba13 Compare May 15, 2026 13:24
@jmagak jmagak force-pushed the RHDHBUGS-2625-Add-section-how-to-disable-SonataFlow-references-for-Orchestrator-plugins-managed-by-Operator branch from f91ba13 to 03b00c1 Compare May 15, 2026 13:49
Copy link
Copy Markdown

@rmarting rmarting left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Before approving it, take a look of the current comments and resolve them.

@jmagak jmagak changed the title RHDHBUGS-2625: Add section how to disable SonataFlow references for Orchestrator plu… RHDHBUGS-2625: Configure Orchestrator to connect to existing PostgreSQL infrastructure May 18, 2026
@jmagak jmagak changed the title RHDHBUGS-2625: Configure Orchestrator to connect to existing PostgreSQL infrastructure RHDHBUGS-2625: Add procedure to configure Orchestrator to connect to existing PostgreSQL infrastructure May 18, 2026
Comment thread modules/shared/snip-create-kubernetes-service-for-external-postgresql.adoc Outdated
Comment thread modules/shared/snip-create-kubernetes-service-for-external-postgresql.adoc Outdated
Comment thread modules/shared/snip-create-kubernetes-service-for-external-postgresql.adoc Outdated
Comment thread modules/shared/snip-create-kubernetes-service-for-external-postgresql.adoc Outdated
@jmagak jmagak force-pushed the RHDHBUGS-2625-Add-section-how-to-disable-SonataFlow-references-for-Orchestrator-plugins-managed-by-Operator branch from 8f1c22b to a02e363 Compare May 18, 2026 13:32
Copy link
Copy Markdown

@rmarting rmarting left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I found valid the current content to configure the Orchestrator with an external database. We are describing here the configuration for an instance managed by the Operator, but that configuration should work in an instance managed by the Helm Chart. At the end, we are defining a ConfigMap for the dynamic plugins and another to inject the configuration to the database.

Maybe we can reuse this PR to describe both process. Is there an idea to have a different PR to describe this process for the Helm Chart? We need to keep in mind that RHDH can be managed in both ways, the documentation should cover them too.

So, what is the plan for the Helm Chart in this case?

@jmagak
Copy link
Copy Markdown
Member Author

jmagak commented May 19, 2026

So, what is the plan for the Helm Chart in this case?

Thanks for the suggestion, @rmarting. I have expanded this PR to include the corresponding documentation for Helm Chart deployments. PTAL.

@jmagak jmagak deployed to internal May 19, 2026 05:14 — with GitHub Actions Active
@sonarqubecloud
Copy link
Copy Markdown

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants