Skip to content

[OSDOCS#17443]Update intros_short descriptions_CQA fixes #112277

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.

Sign up for GitHub

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

Open
jheraght wants to merge 1 commit into
base: main
Choose a base branch
from
Open

[OSDOCS#17443]Update intros_short descriptions_CQA fixes #112277

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
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: 1 addition & 1 deletion modules/rosa-sts-operator-roles.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -8,7 +8,7 @@
= Cluster-specific Operator IAM role reference

[role="_abstract"]
Some cluster capabilities, including several capabilities provided by default, are managed using Operators. Cluster-specific Operator roles use the OpenID Connect (OIDC) provider for the cluster to temporarily authenticate Operator access to AWS resources. Use Operator roles to obtain the temporary permissions forcluster operations, such as managing back-end storage, cloud ingress controller, and external access to a cluster.
Use Operator roles to authenticate to your AWS resources through an OpenID Connect (OIDC) provider, and obtain temporary permissions for cluster operations. Securing these permissions helps you successfully manage capabilities like back-end storage, cloud ingress controllers, and external cluster access.

When you create the Operator roles, the account-wide Operator policies for the matching cluster version are attached to the roles.
ifdef::openshift-rosa[]
Expand Down
2 changes: 1 addition & 1 deletion modules/sd-planning-cluster-maximums-environment.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -8,7 +8,7 @@
= OpenShift Container Platform testing environment and configuration

[role="_abstract"]
The following table lists the OpenShift Container Platform environment and configuration on which the cluster maximums are tested for the AWS cloud platform.
To successfully plan your deployment on the AWS cloud platform, review the tested OpenShift Container Platform environment and configuration settings. Adhering to these cluster maximums ensures your environment is fully supported and optimized for scale.
Copy link
Copy Markdown
Collaborator

@ocpdocs-vale-bot ocpdocs-vale-bot May 26, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🤖 [error] OpenShiftAsciiDoc.SuggestAttribute: Use the AsciiDoc attribute '{product-title}' rather than the plain text product term 'OpenShift Container Platform', unless your use case is an exception.


[options="header",cols="8*"]
|===
Expand Down
11 changes: 2 additions & 9 deletions modules/sd-planning-cluster-maximums.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -8,21 +8,14 @@
= Cluster maximums

[role="_abstract"]
Consider the following tested object maximums when you plan
Review the tested object maximums when planning
ifdef::openshift-rosa[]
a {product-title}
endif::[]
ifdef::openshift-dedicated[]
an {product-title}
endif::[]
cluster installation. The table specifies the maximum limits for each tested type in
ifdef::openshift-rosa[]
a {product-title}
endif::[]
ifdef::openshift-dedicated[]
an {product-title}
endif::[]
cluster.
cluster installation. Adhering to these supported limits helps you successfully architect and deploy a scalable, reliable environment.

These guidelines are based on a cluster of 249 compute (also known as worker) nodes in a multiple availability zone configuration. For smaller clusters, the maximums are lower.

Expand Down
4 changes: 1 addition & 3 deletions modules/sd-planning-considerations.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -15,9 +15,7 @@ endif::[]
ifdef::openshift-dedicated[]
an {product-title}
endif::[]
cluster, the sizing of the control plane and infrastructure nodes are automatically determined by the compute node count.

If you change the number of compute nodes in your cluster after installation, the Red{nbsp}Hat Site Reliability Engineering (SRE) team scales the control plane and infrastructure nodes as required to maintain cluster stability.
cluster, the sizing of the control plane and infrastructure nodes are automatically determined by the compute node count. To maintain cluster stability, the Red{nbsp}Hat Site Reliability Engineering (SRE) team automatically adjusts your control plane and infrastructure nodes whenever you change your compute node count.

[id="node-sizing-during-installation_{context}"]
== Node sizing during installation
Expand Down
2 changes: 1 addition & 1 deletion osd_planning/osd-limits-scalability.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -8,7 +8,7 @@ include::_attributes/attributes-openshift-dedicated.adoc[]
toc::[]

[role="_abstract"]
This document details the tested cluster maximums for {product-title} clusters, along with information about the test environment and configuration used to test the maximums. Information about control plane and infrastructure node sizing and scaling is also provided.
To architect a stable and fully supported {product-title} cluster, review the information about tested cluster maximums, the test environment, and configuration. Understanding these cluster maximums and the recommended control plane and infrastructure node sizing ensures your environment is optimized for scale.

include::modules/sd-planning-cluster-maximums.adoc[leveloffset=+1]
include::modules/sd-planning-cluster-maximums-environment.adoc[leveloffset=+1]
Expand Down
2 changes: 1 addition & 1 deletion rosa_planning/rosa-planning-environment.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -7,7 +7,7 @@ include::_attributes/attributes-openshift-dedicated.adoc[]
toc::[]

[role="_abstract"]
This document describes how to plan your {product-title} environment based on tested cluster maximums.
Plan your {product-title} environment by reviewing the tested cluster maximums. Adhering to these supported limits ensures that your deployment is reliable and optimized for scale.

include::modules/rosa-planning-environment-cluster-max-overview.adoc[leveloffset=+1]
ifdef::openshift-rosa[]
Expand Down