You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: modules/rosa-sdpolicy-instance-types.adoc
+16-2Lines changed: 16 additions & 2 deletions
Original file line number
Diff line number
Diff line change
@@ -18,10 +18,24 @@ endif::rosa-with-hcp[]
18
18
ifndef::rosa-with-hcp[]
19
19
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.
20
20
21
-
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.
21
+
Multiple availability zone clusters require a minimum of 3 control plane nodes, 3 infrastructure nodes, and 3 worker nodes.
22
22
23
+
Consider the following limitations when deploying and managing workloads:
23
24
24
-
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.
25
+
* You must deploy workloads on worker nodes that exist in the cluster by using {product-title} machine pools.
26
+
* Run workloads that you consider essential on the control plane and infrastructure nodes as daemonsets.
27
+
* 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.
28
+
29
+
Red{nbsp}Hat might notify you and resize the control plane or infrastructure nodes if the {product-title} components are impacted.
30
+
31
+
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.
32
+
33
+
[WARNING]
34
+
====
35
+
Shutting down the underlying infrastructure through the cloud provider console is unsupported and can lead to data loss.
36
+
====
37
+
38
+
See the following Red{nbsp}Hat Operator support section for more information about Red{nbsp}Hat workloads that must be deployed on worker nodes.
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].
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.
66
+
* link:https://docs.openshift.com/rosa/rosa_architecture/rosa_policy_service_definition/rosa-policy-process-security.html[Understanding security for ROSA]
68
67
endif::openshift-rosa-hcp[]
68
+
69
69
ifndef::openshift-rosa-hcp[]
70
-
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.
70
+
* xref:../rosa_policy_service_definition/rosa-policy-process-security.adoc#rosa-policy-process-security[Understanding security for ROSA]
71
71
endif::openshift-rosa-hcp[]
72
72
73
-
* See xref:../rosa_policy_service_definition/rosa-hcp-life-cycle.adoc#rosa-hcp-life-cycle[ROSA life cycle]
73
+
* xref:../rosa_policy_service_definition/rosa-hcp-life-cycle.adoc#rosa-hcp-life-cycle[ROSA life cycle]
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.
78
+
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]
85
79
endif::openshift-rosa-hcp[]
86
80
ifndef::openshift-rosa-hcp[]
87
-
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.
81
+
xref:../rosa_policy_service_definition/rosa-policy-process-security.adoc#rosa-policy-process-security[Understanding process and security for ROSA]
88
82
endif::openshift-rosa-hcp[]
89
-
* See
83
+
90
84
ifdef::openshift-rosa-hcp[]
91
85
link:https://docs.openshift.com/rosa/rosa_policy_service_definition/rosa-life-cycle.html#rosa-life-cycle[ROSA life cycle]
0 commit comments