Adds sizing requirements

Author: jmagak

assemblies/assembly-about-rhdh.adoc

@@ -20,3 +20,4 @@ Use {product} to simplify decision-making through a selection of internally appr
 
 
 include::modules/about/con-benefits-of-rhdh.adoc[leveloffset=+1]
+include::modules/about/ref-rhdh-sizing.adoc[leveloffset=+1]

modules/about/ref-rhdh-sizing.adoc

@@ -0,0 +1,34 @@
+:_mod-docs-content-type: REFERENCE
+[id="rhdh-sizing_{context}"]
+= Sizing requirements for {product}
+
+Scaling the {product} requires significant resource allocation. The following table lists the sizing requirements for installing and running {product}, including {product-short} application, database components, and Operator.
+
+.Recommended sizing for running {product}
+[cols="25%,25%,25%,25%", frame="all", options="header"]
+|===
+|Components
+|{product} application
+|{product} database
+|{product} Operator
+
+|Central Processing Unit (CPU)
+|4 vCPU
+|2 vCPU
+|1 vCPU
+
+|Memory
+|16 GB
+|8 GB
+|1500 Mi
+
+|Storage size
+|2 GB
+|20 GB
+|50 Mi
+
+|Replicas
+|2 or more
+|3 or more
+|1 or more
+|===

titles/about/con_rhdh-sizing.adoc

@@ -0,0 +1,22 @@
+:_newdoc-version: 2.18.3
+:_template-generated: 2024-11-25
+
+:_mod-docs-content-type: CONCEPT
+
+[id="rhdh-sizing_{context}"]
+= rhdh-sizing
+
+Write a short introductory paragraph that provides an overview of the module.
+
+The contents of a concept module give the user descriptions and explanations needed to understand and use a product.
+
+* Look at nouns and noun phrases in related procedure modules and assemblies to find the concepts to explain to users.
+* Explain only things that are visible to users. Even if a concept is interesting, it probably does not require explanation if it is not visible to users.
+* Avoid including action items. Action items belong in procedure modules. However, in some cases a concept or reference can include suggested actions when those actions are simple, are highly dependent on the context of the module, and have no place in any procedure module. In such cases, ensure that the heading of the concept or reference remains a noun phrase and not a gerund.
+
+[role="_additional-resources"]
+.Additional resources
+* A bulleted list of links to other closely-related material. These links can include `link:` and `xref:` macros.
+* For more details on writing concept modules, see the link:https://github.com/redhat-documentation/modular-docs#modular-documentation-reference-guide[Modular Documentation Reference Guide].
+* Use a consistent system for file names, IDs, and titles. For tips, see _Anchor Names and File Names_ in link:https://github.com/redhat-documentation/modular-docs#modular-documentation-reference-guide[Modular Documentation Reference Guide].
+