Skip to content

TELCODOCS-2045 - Fix RDS content omissions and errors #89458

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
Apr 22, 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
Binary file modified images/openshift-telco-core-rds-metallb-service-separation.png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Original file line number Diff line number Diff line change
Expand Up @@ -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::
+
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -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::
+
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -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::
Expand Down