Merge pull request #112648 from lcavalle/TELCODOCS-2820

TELCODOCS-2820: Telco hub RDS update

Author: slovern

modules/telco-hub-acm-observability.adoc

@@ -17,7 +17,7 @@ See the Red Hat Knowledgebase article link:https://access.redhat.com/articles/71
 The below table uses inputs derived from the telco RAN DU RDS and the hub cluster RDS as representative values.
 [NOTE]
 ====
-The following numbers are estimated.
+The following numbers are estimates.
 Tune the values for more accurate results.
 Add an engineering margin, for example +20%, to the results to account for potential estimation inaccuracies.
 

modules/telco-hub-assisted-service.adoc

@@ -11,7 +11,7 @@ The Assisted Service is deployed with the multicluster engine and {rh-rhacm-firs
 
 [NOTE]
 ====
-The following numbers are estimated.
+The following numbers are estimates.
 Tune the values for more accurate results.
 Add an engineering margin, for example +20%, to the results to account for potential estimation inaccuracies.
 ====

modules/telco-hub-cert-manager-operator.adoc

@@ -7,7 +7,7 @@
 = cert-manager Operator
 
 New in this release::
-* cert-manager Operator is a new optional component in this release.
+* No reference design updates in this release.
 
 Description::
 +

modules/telco-hub-managed-cluster-deployment.adoc

@@ -22,7 +22,7 @@ These images are release specific.
 ISO images for each {product-title} release to be deployed must be reachable by the hub cluster and each deployed spoke cluster.
 Only include ISO images which exist on the HTTP server in the `AgentServiceConfig` CR.
 * A container registry hosting all {product-title} and day-2 OLM operator images must be reachable from all deployed spoke clusters.
-The hub configuration includes `kustomize` overlays which you can use to provide the TLS certificates and credentials for a disconnected container registry.
+The hub configuration includes Kustomize overlays which you can use to provide the TLS certificates and credentials for a disconnected container registry.
 
 Engineering considerations::
 * You must create a `Secret` CR with the login information for the cluster baseboard management controller (BMC).

modules/telco-hub-observability.adoc

@@ -12,7 +12,6 @@ To balance performance and data analysis, the monitoring service maintains a sub
 The metrics can be accessed on the hub through a set of different preconfigured dashboards.
 
 Observability installation::
-The primary CR to enable and configure the Observability service is the `MulticlusterObservability` CR, which defines the following settings:
 The primary custom resource (CR) to enable and configure the observability service is the `MulticlusterObservability` CR, which defines the following settings:
 
 * Configurable retention settings.

modules/telco-hub-openshift-data-foundation.adoc

@@ -20,4 +20,4 @@ Limits and requirements::
 {odf-short} IPv4 is supported on dual-stack clusters.
 
 Engineering considerations::
-* Address capacity warnings promptly as recovery can be difficult in case of storage capacity exhaustion, see link:https://access.redhat.com/documentation/en-us/red_hat_openshift_data_foundation/4.15/html-single/planning_your_deployment/index#capacity_planning[Capacity planning].
+* Address capacity warnings promptly as recovery can be difficult in case of storage capacity exhaustion, see link:https://access.redhat.com/documentation/en-us/red_hat_openshift_data_foundation/4.21/html-single/planning_your_deployment/index#capacity_planning[Capacity planning].

modules/telco-hub-scaling-targets.adoc

@@ -11,7 +11,7 @@ The resource requirements for the hub cluster are directly dependent on the numb
 
 The hub cluster reference configuration can support up to 3500 managed {sno} clusters under the following conditions:
 
-* 5 policies for each cluster with hub-side templating configured with a 10 minute evaluation interval.
+* 10 {rh-rhacm} configuration policies (comprising 5 Red Hat-provided policies and up to 5 custom configuration policies) with hub-side templating bound to the 3500 clusters and configured with a 10 minute evaluation interval.
 * Only the following {rh-rhacm} add-ons are enabled:
 ** Policy controller
 ** Observability with the default configuration

modules/telco-hub-software-stack.adoc

@@ -7,52 +7,52 @@
 = Telco hub reference configuration software specifications
 
 [role="_abstract"]
-The telco hub 4.21 solution has been validated using the following Red{nbsp}Hat software products for {product-title} clusters.
+The following y-stream versions were used in validation of the telco hub solution for {product-title} clusters.
 
 [width="100%",cols="62%,38%",options="header",]
 |====
 |Hub Cluster Component
 |Software Version (y-stream)
 
 |{product-title}
-|4.21
+|4.22
 
 |{rh-rhacm-first}
-|2.15^1^
+|2.17
 
 |Local Storage Operator
-|4.21
+|4.22
 
 |cert-manager Operator
-|1.18^3^
+|1.19
 
 |{odf-first}
-|4.20^2^
+|4.21
 
 |{gitops-title}
-|1.19^3^
+|1.20
 
-|{ztp-first}  plugins
-|4.21
+|{ztp-first} plugins
+|4.22
 
 |{mce-short} PolicyGenerator plugin
-|2.10^1^
+|2.17
 
 |{cgu-operator-first}
-|4.21
-
+|4.22
 
 |Cluster Logging Operator
-|6.4
+|6.5
 
 |{oadp-first}
 |The version aligned with the {rh-rhacm} release.
 |====
-. This table will be updated when the aligned {rh-rhacm} version (2.16) is released.
-
-. This table will be updated when the aligned {odf-short} version (4.21) is released.
-
-. This is a platform-agnostic Operator. Its support lifecycle does not extend to the full lifecycle of {product-title}. With all platform agnostic Operators, customers need to anticipate the need to update to a newer minor version of the Operator at the end of the Operator lifecycle of the current version or when planning to update the {product-title} cluster to stay supported. While a given Operator minor version may not support the latest available {product-title} release, there will always be a version of the Operator available for every supported version of {product-title} at any given point in time. For terms of support, see the Platform Agnostic Operators section of link:https://access.redhat.com/support/policy/updates/openshift_operators[OpenShift Operator Life Cycles].
+* {odf-short} will be updated to 4.22 when the aligned {odf-short} version is released.
+* Cluster Logging Operator will be updated to 6.6 when the aligned Cluster Logging Operator version is released.
+* The cert-manager Operator and {gitops-title} Operator are platform agnostic operators. 
+The support lifecycle for these operators is independent from the support lifecycle for {product-title}. 
+You might need to update to a newer minor version of these operators at the end of an operator lifecycle, or when planning to update the {product-title} cluster to continue support. 
+For support lifecycle details for platform agnostic operators, see link:https://access.redhat.com/support/policy/updates/openshift_operators[OpenShift Operator Life Cycles].
 
 
 :leveloffset!: