Skip to content

TELCODOCS-2284: Updates for 4.19 hub cluster with GA support #94468

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Jun 11, 2025
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 0 additions & 2 deletions modules/telco-hub-gitops-operator-and-ztp-plugins.adoc
Original file line number Diff line number Diff line change
Expand Up @@ -19,8 +19,6 @@ To maintain multiple per-version policies simultaneously, use Git to manage the


Limits and requirements::
* 300 single node `SiteConfig` CRs can be synchronized for each ArgoCD application.
You can use multiple applications to achieve the maximum number of clusters supported by a single hub cluster.
* 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.

Engineering considerations::
Expand Down
3 changes: 3 additions & 0 deletions modules/telco-hub-scaling-targets.adoc
Original file line number Diff line number Diff line change
Expand Up @@ -19,6 +19,9 @@ The reference configuration is also validated for deployment and management of a
The specific limits depend on the mix of cluster topologies, enabled {rh-rhacm} features, and so on.
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).

A hub cluster conforming to this reference specification can support synchronization of 1000 single-node `ClusterInstance` CRs for each ArgoCD application.
You can use multiple applications to achieve the maximum number of clusters supported by a single hub cluster.

[NOTE]
====
Specific dimensioning requirements are highly dependent on the cluster topology and workload.
Expand Down
10 changes: 5 additions & 5 deletions modules/telco-hub-software-stack.adoc
Original file line number Diff line number Diff line change
Expand Up @@ -15,10 +15,10 @@ The telco hub {product-version} solution has been validated using the following
|Component |Software version

|{product-title}
|4.18
|4.19

|Local Storage Operator
|4.18
|4.19

|{odf-first}
|4.18
Expand All @@ -27,16 +27,16 @@ The telco hub {product-version} solution has been validated using the following
|2.13

|{gitops-title}
|1.15
|1.16

|{ztp-first} plugins
|4.18
|4.19

|{mce-short} PolicyGenerator plugin
|2.12

|{cgu-operator-first}
|4.18
|4.19

|Cluster Logging Operator
|6.2
Expand Down
5 changes: 1 addition & 4 deletions scalability_and_performance/telco-hub-rds.adoc
Original file line number Diff line number Diff line change
Expand Up @@ -9,9 +9,6 @@ toc::[]

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.

:FeatureName: The telco hub RDS
include::snippets/technology-preview.adoc[]

include::modules/telco-ran-core-ref-design-spec.adoc[leveloffset=+1]

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

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

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