Merge branch 'main' into RHIDP-8634-3

Author: Gerry-Forde

artifacts/attributes.adoc

@@ -87,8 +87,8 @@
 :eks-brand-name: Amazon Elastic Kubernetes Service
 :eks-name: Elastic Kubernetes Service
 :eks-short: EKS
-:gcp-brand-name: Google Cloud Platform
-:gcp-short: GCP
+:gcp-brand-name: Google Cloud
+:gcp-short: Google Cloud
 :gke-brand-name: Google Kubernetes Engine
 :gke-short: GKE
 

assemblies/assembly-install-rhdh-osd-gcp.adoc

@@ -4,7 +4,7 @@
 = Installing {product} on {osd-short} on {gcp-brand-name}
 :context: assembly-install-rhdh-osd-gcp
 
-You can install {product-short} on {osd-short} on {gcp-brand-name} ({gcp-short}) using one of the following methods:
+You can install {product-short} on {osd-short} on {gcp-brand-name} using one of the following methods:
 
 * The {product} Operator
 * The {product} Helm chart

assemblies/assembly-model-context-protocol-tools.adoc

@@ -12,8 +12,6 @@ include::modules/model-context-protocol-tools/proc-configuring-model-context-pro
 
 include::modules/model-context-protocol-tools/proc-configuring-mcp-clients-to-access-the-rhdh-server.adoc[leveloffset=+2]
 
-include::modules/model-context-protocol-tools/proc-configuring-mcp-tools-for-developer-lightspeed.adoc[leveloffset=+1]
-
 include::assembly-using-the-mcp-tools-to-access-data.adoc[leveloffset=+1]
 
 include::assembly-troubleshooting-mcp-server-and-client-problems.adoc[leveloffset=+1]

assemblies/assembly-orchestrator-rhdh.adoc

@@ -24,7 +24,6 @@ To start using Orchestrator in {product-very-short}, you must:
 
 * Install the required infrastructure components, such as Red Hat OpenShift Serverless Operator, Knative Serving, Knative Eventing, and OpenShift Serverless Logic Operator
 * Configure your {product-custom-resource-type} custom resource (CR) or Helm values file for Orchestrator
-* Import the Orchestrator software templates into the {product} catalog
 
 // orchestrator architecture
 include::modules/orchestrator/con-architecture-overview.adoc[leveloffset=+1]
@@ -48,4 +47,4 @@ include::modules/orchestrator/proc-manual-install-components-orchestrator-plugin
 include::modules/orchestrator/proc-helper-script-overview.adoc[leveloffset=+2]
 
 // best practices when creating workflows
-include::modules/orchestrator/ref-best-practices-for-creating-workflows.adoc[leveloffset=+1]
+include::modules/orchestrator/ref-best-practices-for-creating-workflows.adoc[leveloffset=+1]

modules/about/ref-rhdh-sizing.adoc

@@ -3,7 +3,9 @@
 [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.
+Learn about sizing requirements for {product}.
+Table 1 lists the sizing requirements for installing and running {product}, including {product-short} application, database components, and Operator.
+Table 2 lists recommended sizing requirements for {product-docs-link}/html-single/configuring_red_hat_developer_hub/index#configuring-external-postgresql-databases[external PostgreSQL deployment] based on the deployment scale.
 
 .Recommended sizing for running {product}
 [cols="25%,25%,25%,25%", frame="all", options="header"]
@@ -33,3 +35,53 @@ Scaling the {product} requires significant resource allocation. The following ta
 |3 or more
 |1 or more
 |===
+
+.Recommended sizing for external PostgreSQL deployments with {product}
+[cols="25%,25%,25%,25%,25%", frame="all", options="header"]
+|===
+|Sizing legend
+|Small-scale
+|Mid-scale
+|Large-scale
+|Enterprise-scale
+
+|Application usage
+|up to 5 thousand entities, up to 50 concurrent users
+|5–20 thousand entities, 50–150 concurrent users
+|20–50 thousand entities, 150–400 concurrent users
+|50–150 thousand entities, 400–800 concurrent users
+
+|vCPU
+|2
+|4
+|8
+|16
+
+|Memory
+|8 GiB
+|16 GiB
+|32 GiB
+|64 GiB
+
+|Storage
+|50 GiB
+|100 GiB
+|200 GiB
+|500 GiB
+
+|Number of replicas
+|1
+|2
+|2-3
+|3+
+
+|PostgreSQL Database HA
+|1 primary
+|1 primary, 1 standby
+|1 primary, 1 synchronous standby
+|1 primary, 1 synchronous standby, 1 asynchronous replica
+|===
+
+
+
+

modules/authorization/proc-configuring-the-RBAC-backend-plugin.adoc

@@ -6,7 +6,7 @@
 You can configure the RBAC backend plugin by updating the `{my-app-config-file}` file to enable the permission framework.
 
 .Prerequisites
-* You have installed the `@janus-idp/backstage-plugin-rbac` plugin in {product-short}. For more information, see {configuring-dynamic-plugins-book-link}[{configuring-dynamic-plugins-book-title}].
+* You have installed the `@backstage-community/plugin-rbac` plugin in {product-short}. For more information, see {configuring-dynamic-plugins-book-link}[{configuring-dynamic-plugins-book-title}].
 
 .Procedure
 * Update the `{my-app-config-file}` file to enable the permission framework as shown:

modules/authorization/proc-setting-up-the-guest-authentication-provider.adoc

@@ -6,7 +6,7 @@
 You can enable guest authentication and use it alongside the RBAC frontend plugin.
 
 .Prerequisites
-* You have installed the `@janus-idp/backstage-plugin-rbac` plugin in {product-short}. For more information, see {configuring-dynamic-plugins-book-link}[{configuring-dynamic-plugins-book-title}].
+* You have installed the `@backstage-community/plugin-rbac` plugin in {product-short}. For more information, see {configuring-dynamic-plugins-book-link}[{configuring-dynamic-plugins-book-title}].
 
 .Procedure
 

modules/authorization/ref-rbac-permission-policies.adoc

@@ -219,6 +219,7 @@ conditions:
       key: type
       value: kubernetes-cluster
 ----
+OCM permissions::
 
 [cols="15%,25%,15%,45%", frame="all", options="header"]
 |===

modules/configuring-external-databases/proc-configuring-postgresql-instance-using-helm.adoc

@@ -7,6 +7,7 @@ You can configure an external PostgreSQL instance by using the Helm Chart. By de
 
 .Prerequisites
 
+* You meet the {about-book-link}#rhdh-sizing_about-rhdh[Sizing requirements for external PostgreSQL deployments].
 * You are using a supported version of PostgreSQL. For more information, see the link:https://access.redhat.com/support/policy/updates/developerhub[Product life cycle page].
 * You have the following details:
 ** `db-host`: Denotes your PostgreSQL instance Domain Name System (DNS) or IP address

modules/configuring-external-databases/proc-configuring-postgresql-instance-using-the-operator.adoc

@@ -7,6 +7,7 @@ You can configure an external PostgreSQL instance using the {product} Operator.
 
 .Prerequisites
 
+* You meet the {about-book-link}#rhdh-sizing_about-rhdh[Sizing requirements for external PostgreSQL deployments].
 * You are using a supported version of PostgreSQL. For more information, see the link:https://access.redhat.com/support/policy/updates/developerhub[Product life cycle page].
 * You have the following details:
 ** `db-host`: Denotes your PostgreSQL instance Domain Name System (DNS) or IP address