openshift/openshift-docs
1
0
Fork 0
mirror of https://github.com/openshift/openshift-docs.git synced 2026-02-07 09:46:53 +01:00
Code Issues Releases Activity

instance_type_doc_updates

Browse Source
This commit is contained in:
mletalie
2024-12-20 14:02:36 -05:00
committed by openshift-cherrypick-robot
parent 47b6e91a64
commit d4581ef0eb
3 changed files with 30 additions and 22 deletions
Download Patch File Download Diff File Expand all files Collapse all files

18
modules/rosa-sdpolicy-instance-types.adoc
View File

@@ -18,10 +18,24 @@ 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.
Consider the following limitations when deploying and managing workloads:
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.
* You must deploy workloads on worker nodes that exist in the cluster by using {product-title} machine pools.
* Run workloads that you consider essential on the control plane and infrastructure nodes as daemonsets.
* You must ensure that any workloads running on these nodes are secure, scalable, and compatible with a version of {product-title}, so that the Service Level Agreement (SLA) for API server availability is not impacted.
Red{nbsp}Hat might notify you and resize the control plane or infrastructure nodes if the {product-title} components are impacted.
Control plane and infrastructure nodes are deployed and managed by Red{nbsp}Hat. These nodes are automatically resized based on the resource use. If you need to resize these nodes to meet cluster demands, open a support case.
[WARNING]
====
Shutting down the underlying infrastructure through the cloud provider console is unsupported and can lead to data loss.
====
See the following Red{nbsp}Hat Operator support section for more information about Red{nbsp}Hat workloads that must be deployed on worker nodes.
endif::rosa-with-hcp[]
[NOTE]

16
rosa_architecture/rosa_policy_service_definition/rosa-hcp-service-definition.adoc
View File

@@ -26,7 +26,7 @@ include::modules/rosa-sdpolicy-instance-types.adoc[leveloffset=+2]
[role="_additional-resources"]
.Additional resources
For a detailed listing of supported instance types, see xref:../rosa_policy_service_definition/rosa-hcp-instance-types.adoc#rosa-hcp-instance-types[{hcp-title} instance types].
* xref:../rosa_policy_service_definition/rosa-hcp-instance-types.adoc#rosa-hcp-instance-types[{hcp-title} instance types]
include::modules/rosa-sdpolicy-am-regions-az.adoc[leveloffset=+2]
@@ -46,7 +46,7 @@ include::modules/rosa-sdpolicy-networking.adoc[leveloffset=+1]
[role="_additional-resources"]
.Additional resources
* For more information about the network verification checks, see
* For more information about the network verification checks, see
ifdef::openshift-rosa-hcp[]
link:https://docs.openshift.com/rosa/networking/network-verification.html#network-verification[Network verification].
endif::openshift-rosa-hcp[]
@@ -62,12 +62,12 @@ include::modules/rosa-sdpolicy-security.adoc[leveloffset=+1]
[id="additional-resources_rosa-hcp-service-definition"]
== Additional resources
* See
ifdef::openshift-rosa-hcp[]
link:https://docs.openshift.com/rosa/rosa_policy_service_definition/rosa-policy-process-security.html#rosa-policy-process-security[Understanding process and security for ROSA] for the latest compliance information.
endif::openshift-rosa-hcp[]
ifndef::openshift-rosa-hcp[]
xref:../rosa_policy_service_definition/rosa-policy-process-security.adoc#rosa-policy-process-security[Understanding process and security for ROSA] for the latest compliance information.
* link:https://docs.openshift.com/rosa/rosa_architecture/rosa_policy_service_definition/rosa-policy-process-security.html[Understanding security for ROSA]
endif::openshift-rosa-hcp[]
* See xref:../rosa_policy_service_definition/rosa-hcp-life-cycle.adoc#rosa-hcp-life-cycle[ROSA life cycle]
ifndef::openshift-rosa-hcp[]
* xref:../rosa_policy_service_definition/rosa-policy-process-security.adoc#rosa-policy-process-security[Understanding security for ROSA]
endif::openshift-rosa-hcp[]
* xref:../rosa_policy_service_definition/rosa-hcp-life-cycle.adoc#rosa-hcp-life-cycle[ROSA life cycle]

18
rosa_architecture/rosa_policy_service_definition/rosa-service-definition.adoc
View File

@@ -31,19 +31,14 @@ include::modules/rosa-sdpolicy-instance-types.adoc[leveloffset=+2]
[role="_additional-resources"]
.Additional resources
For a detailed listing of supported instance types, see
ifdef::openshift-rosa-hcp[]
xref:../rosa_policy_service_definition/rosa-hcp-instance-types.adoc#rosa-instance-types[{product-title} instance types].
* xref:../rosa_policy_service_definition/rosa-hcp-instance-types.adoc#rosa-instance-types[{product-title} instance types].
endif::openshift-rosa-hcp[]
ifndef::openshift-rosa-hcp[]
xref:../rosa_policy_service_definition/rosa-instance-types.adoc#rosa-instance-types[{product-title} instance types].
endif::openshift-rosa-hcp[]
* xref:../rosa_policy_service_definition/rosa-instance-types.adoc#rosa-instance-types[{product-title} instance types]
* xref:../../rosa_planning/rosa-limits-scalability.adoc#rosa-limits-scalability[Limits and scalability]
For a detailed listing of supported instance types, see
endif::openshift-rosa-hcp[]
include::modules/rosa-sdpolicy-am-regions-az.adoc[leveloffset=+2]
@@ -63,7 +58,7 @@ include::modules/rosa-sdpolicy-networking.adoc[leveloffset=+1]
[role="_additional-resources"]
.Additional resources
* For more information about the network verification checks, see
* For more information about the network verification checks, see
ifdef::openshift-rosa-hcp[]
link:https://docs.openshift.com/rosa/networking/network-verification.html#network-verification[Network verification].
endif::openshift-rosa-hcp[]
@@ -79,14 +74,13 @@ include::modules/rosa-sdpolicy-security.adoc[leveloffset=+1]
[id="additional-resources_rosa-service-definition"]
== Additional resources
* See
ifdef::openshift-rosa-hcp[]
link:https://docs.openshift.com/rosa/rosa_policy_service_definition/rosa-policy-process-security.html#rosa-policy-process-security[Understanding process and security for ROSA] for the latest compliance information.
link:https://docs.openshift.com/rosa/rosa_policy_service_definition/rosa-policy-process-security.html#rosa-policy-process-security[Understanding process and security for ROSA]
endif::openshift-rosa-hcp[]
ifndef::openshift-rosa-hcp[]
xref:../rosa_policy_service_definition/rosa-policy-process-security.adoc#rosa-policy-process-security[Understanding process and security for ROSA] for the latest compliance information.
xref:../rosa_policy_service_definition/rosa-policy-process-security.adoc#rosa-policy-process-security[Understanding process and security for ROSA]
endif::openshift-rosa-hcp[]
* See
ifdef::openshift-rosa-hcp[]
link:https://docs.openshift.com/rosa/rosa_policy_service_definition/rosa-life-cycle.html#rosa-life-cycle[ROSA life cycle]
endif::openshift-rosa-hcp[]