RHIDP-8629: sizing requirements for external PostgreSQL deployment with RHDH

[deerskindoll]

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

Version(s):

main, release-1.8

Issue:

RHIDP-8629
Preview:

4. Sizing requirements for Red Hat Developer Hub

3. Configuring external PostgreSQL databases

[Fortune-Ndlovu]

Thanks for pushing this PR @deerskindoll, can we fix CI so I can also review the preview, otherwise looks good

[rhdh-bot]

Updated preview: https://redhat-developer.github.io/red-hat-developers-documentation-rhdh/pr-1449/ @ 11/06/25 12:06:05

[deerskindoll]

@Fortune-Ndlovu sorry for the long response time, the preview is available now. I'm aware of the issue with additional text appears in the table. it's not in the source file and I'll be checking how to remove it from the preview

[Fortune-Ndlovu]

simple, fix, the rest of the numbers look good, thanks.

[Fortune-Ndlovu]

this should fix the syntax error within the table structure

[deerskindoll]

this should fix the syntax error within the table structure

thank you very much for the fix. I see that I didn't close the table properly

[Fortune-Ndlovu]

/lgtm

[openshift-ci]

New changes are detected. LGTM label has been removed.

[jmagak]

A few suggestions.

[jmagak]

Suggested change

	* You meet the sizing requirements listed in Table 4.2 Recommended sizing for external PostgreSQL deployments with {product} in {product-docs-link}/single-html/about_red_hat_developer_hub/index#rhdh-sizing_about-rhdh[Sizing requirements for {product}]
	* You meet the sizing requirements listed in Table 4.2 Recommended sizing for external PostgreSQL deployments with {product} in {product-docs-link}/single-html/about_red_hat_developer_hub/index#rhdh-sizing_about-rhdh[Sizing requirements for {product}].

I am afraid the user might have trouble navigating to the table in the mentioned section, making it difficult to find the information. Could we instead provide a direct link to the 4.2 table? If the table is already included in Sizing requirements for Red Hat Developer Hub, we can avoid repeating it.

[deerskindoll]

good point. let me check how to do it.

@themr0c can you please help me? the tables aren't separate modules, how do I link to them directly? do I have to move them to modules?

[jmagak]

Suggested change

	* You meet the sizing requirements listed in Table 4.2 Recommended sizing for external PostgreSQL deployments with {product} in {product-docs-link}/single-html/about_red_hat_developer_hub/index#rhdh-sizing_about-rhdh[Sizing requirements for {product}]
	* You meet the sizing requirements listed in Table 4.2 Recommended sizing for external PostgreSQL deployments with {product} in {product-docs-link}/single-html/about_red_hat_developer_hub/index#rhdh-sizing_about-rhdh[Sizing requirements for {product}].

Same comment as above.

[deerskindoll]

/cherry-pick release-1.8

[openshift-cherrypick-robot]

@deerskindoll: only redhat-developer org members may request cherry picks. If you are already part of the org, make sure to change your membership to public. Otherwise you can still do the cherry-pick manually.

In response to this:

/cherry-pick release-1.8

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.