Skip to content

Commit 338727d

Browse files
committed
TELCODOCS-2284: Updates for 4.19 hub cluster with GA support
1 parent 3573457 commit 338727d

File tree

4 files changed

+8
-10
lines changed

4 files changed

+8
-10
lines changed

modules/telco-hub-gitops-operator-and-ztp-plugins.adoc

Lines changed: 0 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -19,8 +19,6 @@ To maintain multiple per-version policies simultaneously, use Git to manage the
1919

2020

2121
Limits and requirements::
22-
* 300 single node `SiteConfig` CRs can be synchronized for each ArgoCD application.
23-
You can use multiple applications to achieve the maximum number of clusters supported by a single hub cluster.
2422
* To ensure consistent and complete cleanup of managed clusters and their associated resources during cluster or node deletion, you must configure ArgoCD to use background deletion mode.
2523

2624
Engineering considerations::

modules/telco-hub-scaling-targets.adoc

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -19,6 +19,9 @@ The reference configuration is also validated for deployment and management of a
1919
The specific limits depend on the mix of cluster topologies, enabled {rh-rhacm} features, and so on.
2020
In a mixed topology scenario, the reference hub configuration is validated with a combination of 1200 {sno} clusters, 400 compact clusters (3 nodes combined control plane and compute nodes), and 230 standard clusters (3 control plane and 2 worker nodes).
2121

22+
A hub cluster conforming to this reference specification can support synchronization of 1000 single-node `ClusterInstance` CRs for each ArgoCD application.
23+
You can use multiple applications to achieve the maximum number of clusters supported by a single hub cluster.
24+
2225
[NOTE]
2326
====
2427
Specific dimensioning requirements are highly dependent on the cluster topology and workload.

modules/telco-hub-software-stack.adoc

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -15,10 +15,10 @@ The telco hub {product-version} solution has been validated using the following
1515
|Component |Software version
1616

1717
|{product-title}
18-
|4.18
18+
|4.19
1919

2020
|Local Storage Operator
21-
|4.18
21+
|4.19
2222

2323
|{odf-first}
2424
|4.18
@@ -30,13 +30,13 @@ The telco hub {product-version} solution has been validated using the following
3030
|1.15
3131

3232
|{ztp-first} plugins
33-
|4.18
33+
|4.19
3434

3535
|{mce-short} PolicyGenerator plugin
3636
|2.12
3737

3838
|{cgu-operator-first}
39-
|4.18
39+
|4.19
4040

4141
|Cluster Logging Operator
4242
|6.2

scalability_and_performance/telco-hub-rds.adoc

Lines changed: 1 addition & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -9,9 +9,6 @@ toc::[]
99

1010
The telco hub reference design specifications (RDS) describes the configuration for a hub cluster that deploys and operates fleets of {product-title} clusters in a telco environment.
1111

12-
:FeatureName: The telco hub RDS
13-
include::snippets/technology-preview.adoc[]
14-
1512
include::modules/telco-ran-core-ref-design-spec.adoc[leveloffset=+1]
1613

1714
include::modules/telco-deviations-from-the-ref-design.adoc[leveloffset=+1]
@@ -222,7 +219,7 @@ include::modules/telco-hub-oadp-operator.adoc[leveloffset=+2]
222219
[id="telco-yaml-reference_{context}"]
223220
== Hub cluster reference configuration CRs
224221

225-
The following is the complete YAML reference of all the custom resources (CRs) for the telco management hub reference configuration in 4.18.
222+
The following is the complete YAML reference of all the custom resources (CRs) for the telco management hub reference configuration in 4.19.
226223

227224
[id="telco-hub-rhacm-ref-crs_{context}"]
228225
=== {rh-rhacm} reference YAML

0 commit comments

Comments
 (0)