mirror of
https://github.com/openshift/openshift-docs.git
synced 2026-02-05 21:46:22 +01:00
53 lines
3.0 KiB
Plaintext
53 lines
3.0 KiB
Plaintext
|
|
// Module included in the following assemblies:
|
|
//
|
|
// * rosa_architecture/rosa_policy_service_definition/rosa-service-definition.adoc
|
|
// * rosa_architecture/rosa_policy_service_definition/rosa-hcp-service-definition.adoc
|
|
|
|
ifeval::["{context}" == "rosa-hcp-service-definition"]
|
|
:rosa-with-hcp:
|
|
endif::[]
|
|
|
|
:_mod-docs-content-type: CONCEPT
|
|
[id="rosa-sdpolicy-instance-types_{context}"]
|
|
= Instance types
|
|
|
|
ifdef::rosa-with-hcp[]
|
|
All {hcp-title} clusters require a minimum of 2 worker nodes. Shutting down the underlying infrastructure through the cloud provider console is unsupported and can lead to data loss.
|
|
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.
|
|
|
|
Consider the following limitations when deploying and managing workloads:
|
|
|
|
* 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]
|
|
====
|
|
Approximately one vCPU core and 1 GiB of memory are reserved on each worker node and removed from allocatable resources. This reservation of resources is necessary to run processes required by the underlying platform. These processes include system daemons such as udev, kubelet, and container runtime among others. The reserved resources also account for kernel reservations.
|
|
|
|
{OCP} core systems such as audit log aggregation, metrics collection, DNS, image registry, SDN, and others might consume additional allocatable resources to maintain the stability and maintainability of the cluster. The additional resources consumed might vary based on usage.
|
|
|
|
For additional information, see the link:https://kubernetes.io/docs/tasks/administer-cluster/reserve-compute-resources/#system-reserved[Kubernetes documentation].
|
|
====
|
|
|
|
ifeval::["{context}" == "rosa-hcp-service-definition"]
|
|
:!rosa-with-hcp:
|
|
endif::[]
|