RDS content fixes

2026-02-05 12:46:18 +01:00 · 2025-03-03 16:33:02 +00:00
parent f9ef970ef5
commit baaf678f74
4 changed files with 6 additions and 2 deletions
--- a/images/openshift-telco-core-rds-metallb-service-separation.png
+++ b/images/openshift-telco-core-rds-metallb-service-separation.png
--- a/modules/telco-core-red-hat-advanced-cluster-management.adoc
+++ b/modules/telco-core-red-hat-advanced-cluster-management.adoc
@@ -7,7 +7,7 @@
 = Red Hat Advanced Cluster Management

 New in this release::
-* No reference design updates in this release
+* Image-based installation for {sno} clusters is the recommended install methodology.

 Description::
 +
--- a/modules/telco-ran-engineering-considerations-for-the-ran-du-use-model.adoc
+++ b/modules/telco-ran-engineering-considerations-for-the-ran-du-use-model.adoc
@@ -65,7 +65,7 @@ $ query=avg_over_time(pod:container_cpu_usage:sum{namespace="openshift-kube-apis
 ----
 ====
 . Application logs are not collected by the platform log collector
-. Aggregate traffic on the primary CNI is less than 8 MBps
+. Aggregate traffic on the primary CNI is less than 8 Mbps

 Hub cluster management characteristics::
 +
--- a/modules/telco-ran-red-hat-advanced-cluster-management-rhacm.adoc
+++ b/modules/telco-ran-red-hat-advanced-cluster-management-rhacm.adoc
@@ -20,6 +20,10 @@ You manage cluster configuration and upgrades declaratively by applying `Policy`
 * Zero touch provisioning (ZTP) of clusters using the MCE component in {rh-rhacm}.
 * Configuration, upgrades, and cluster status through the {rh-rhacm} policy controller.
 * During managed cluster installation, {rh-rhacm} can apply labels to individual nodes as configured through the `ClusterInstance` CR.
+
+The recommended method for {sno} cluster installation is the image-based installer method available in MCE using the `ClusterInstance` CR for cluster definition.
+
+The recommended method for {sno} cluster upgrade is the image-based upgrade method.
 --

 Limits and requirements::