Skip to content

Commit

Permalink
instance_type_doc_updates
Browse files Browse the repository at this point in the history
  • Loading branch information
mletalie committed Dec 20, 2024
1 parent abe718d commit 0dd53de
Show file tree
Hide file tree
Showing 2 changed files with 5 additions and 5 deletions.
6 changes: 3 additions & 3 deletions modules/rosa-sdpolicy-instance-types.adoc
Original file line number Diff line number Diff line change
Expand Up @@ -18,10 +18,10 @@ endif::rosa-with-hcp[]
ifndef::rosa-with-hcp[]
Single availability zone clusters require a minimum of 3 control plane nodes, 2 infrastructure nodes, and 2 worker nodes deployed to a single availability zone.

Multiple availability zone clusters require a minimum of 3 control plane nodes, 3 infrastructure nodes, and 3 worker nodes. Additional nodes must be purchased in multiples of three to maintain proper node distribution.
Multiple availability zone clusters require a minimum of 3 control plane nodes, 3 infrastructure nodes, and 3 worker nodes.


Control plane and infrastructure nodes are deployed and managed by Red{nbsp}Hat. Shutting down the underlying infrastructure through the cloud provider console is unsupported and can lead to data loss. There are at least 3 control plane nodes that handle etcd- and API-related workloads. There are at least 2 infrastructure nodes that handle metrics, routing, the web console, and other workloads. You must not run any workloads on the control and infrastructure nodes. Any workloads you intend to run must be deployed on worker nodes. See the Red{nbsp}Hat Operator support section below for more information about Red{nbsp}Hat workloads that must be deployed on worker nodes.
Control plane and infrastructure nodes are deployed and managed by Red{nbsp}Hat; these nodes are automatically resized based on the resource utilization. To proactively resize these nodes in anticipation of change in cluster utilization, open a support case. Shutting down the underlying infrastructure through the cloud provider console is unsupported and can lead to data loss. Workloads must be deployed on the worker nodes deployed in the cluster using {product-title} machine pools. You may only run node-level workloads (daemonsets) on the Control Plane and Infrastructure nodes. You will be responsible for such workloads deployed on these nodes in ensuring they are secure, performant, and compatible with OpenShift versions so that the Service Level Agreement (SLA) for API Server Availability is not affected. Red{nbsp}Hat may notify you and resize the control plane or infrastructure nodes if the OpenShift components are impacted.
See the Red{nbsp}Hat Operator support section below for more information about Red{nbsp}Hat workloads that must be deployed on worker nodes.
endif::rosa-with-hcp[]

[NOTE]
Expand Down
4 changes: 2 additions & 2 deletions modules/sdpolicy-am-compute.adoc
Original file line number Diff line number Diff line change
Expand Up @@ -7,14 +7,14 @@

Single availability zone clusters require a minimum of 2 worker nodes for Customer Cloud Subscription (CCS) clusters deployed to a single availability zone. A minimum of 4 worker nodes is required for standard clusters. These 4 worker nodes are included in the base subscription.

Multiple availability zone clusters require a minimum of 3 worker nodes for Customer Cloud Subscription (CCS) clusters, 1 deployed to each of 3 availability zones. A minimum of 9 worker nodes are required for standard clusters. These 9 worker nodes are included in the base subscription, and additional nodes must be purchased in multiples of 3 to maintain proper node distribution.
Multiple availability zone clusters require a minimum of 3 worker nodes for Customer Cloud Subscription (CCS) clusters, 1 deployed to each of 3 availability zones. A minimum of 9 worker nodes are required for standard clusters. These 9 worker nodes are included in the base subscription.

[NOTE]
====
All worker nodes within a single {product-title} machine pool must be of the same type and size. However, worker nodes across multiple machine pools within an {product-title} cluster can be of different types and sizes.
====

Control plane and infrastructure nodes are also provided by Red Hat. There are at least 3 control plane nodes that handle etcd and API-related workloads. There are at least 2 infrastructure nodes that handle metrics, routing, the web console, and other workloads. You must not run any workloads on the control plane and infrastructure nodes. Any workloads you intend to run must be deployed on worker nodes. See the Red Hat Operator support section below for more information about Red Hat workloads that must be deployed on worker nodes.
Control plane and infrastructure nodes are deployed and managed by Red {nbsp} Hat. There are at least 3 control plane nodes that handle etcd and API-related workloads. There are at least 2 infrastructure nodes that handle metrics, routing, the web console, and other workloads. You must not run any workloads on the control plane and infrastructure nodes. Any workloads you intend to run must be deployed on worker nodes. See the Red Hat Operator support section below for more information about Red Hat workloads that must be deployed on worker nodes.

[NOTE]
====
Expand Down

0 comments on commit 0dd53de

Please sign in to comment.