RHDHBUGS-2625: Add procedure to configure Orchestrator to connect to existing PostgreSQL infrastructure#2199
Conversation
PR Build ResultsBuild passed -- 34/34 titles | 71s Content Quality AssessmentCQA Report
SummaryChecks: 19 total, 19 pass, 0 fail 19 checks: 19 pass, 0 fail Run Updated 2026-05-19 05:16:31 UTC |
abcd177 to
26474f9
Compare
1ddeeb7 to
f91ba13
Compare
f91ba13 to
03b00c1
Compare
rmarting
left a comment
There was a problem hiding this comment.
Before approving it, take a look of the current comments and resolve them.
8f1c22b to
a02e363
Compare
rmarting
left a comment
There was a problem hiding this comment.
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?
Thanks for the suggestion, @rmarting. I have expanded this PR to include the corresponding documentation for Helm Chart deployments. PTAL. |
|



…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