mirror of
https://github.com/openshift/openshift-docs.git
synced 2026-02-06 06:46:26 +01:00
01fade44b2
Updates for Max David's comments Adding merge comparison Reorg for clarity Updates for David
47 lines
2.7 KiB
Plaintext
47 lines
2.7 KiB
Plaintext
[id="ztp-sno-additional-worker-node"]
|
|
= Expanding {sno} clusters with {ztp}
|
|
include::_attributes/common-attributes.adoc[]
|
|
:context: sno-additional-worker
|
|
|
|
toc::[]
|
|
|
|
You can expand {sno} clusters with {ztp-first}. When you add worker nodes to {sno} clusters, the original {sno} cluster retains the control plane node role. Adding worker nodes does not require any downtime for the existing {sno} cluster.
|
|
|
|
[NOTE]
|
|
====
|
|
Although there is no specified limit on the number of worker nodes that you can add to a {sno} cluster, you must revaluate the reserved CPU allocation on the control plane node for the additional worker nodes.
|
|
====
|
|
|
|
If you require workload partitioning on the worker node, you must deploy and remediate the managed cluster policies on the hub cluster before installing the node. This way, the workload partitioning `MachineConfig` objects are rendered and associated with the `worker` machine config pool before the {ztp} workflow applies the `MachineConfig` ignition file to the worker node.
|
|
|
|
It is recommended that you first remediate the policies, and then install the worker node.
|
|
If you create the workload partitioning manifests after installing the worker node, you must drain the node manually and delete all the pods managed by daemon sets. When the managing daemon sets create the new pods, the new pods undergo the workload partitioning process.
|
|
|
|
:FeatureName: Adding worker nodes to {sno} clusters with {ztp}
|
|
include::snippets/technology-preview.adoc[]
|
|
|
|
[role="_additional-resources"]
|
|
.Additional resources
|
|
|
|
* For more information about {sno} clusters tuned for vDU application deployments, see xref:../edge_computing/ztp-reference-cluster-configuration-for-vdu.adoc#sno-configure-for-vdu[Reference configuration for deploying vDUs on {sno}].
|
|
|
|
* For more information about worker nodes, see xref:../nodes/nodes/nodes-sno-worker-nodes.adoc#nodes-sno-worker-nodes[Adding worker nodes to {sno} clusters].
|
|
|
|
* For information about removing a worker node from an expanded {sno} cluster, see link:https://access.redhat.com/documentation/en-us/red_hat_advanced_cluster_management_for_kubernetes/2.10/html/clusters/cluster_mce_overview#auto-remove-host-steps-cli[Removing managed cluster nodes by using the command line interface].
|
|
|
|
include::modules/ztp-worker-node-applying-du-profile.adoc[leveloffset=+1]
|
|
|
|
include::modules/ztp-worker-node-daemon-selector-compatibility.adoc[leveloffset=+1]
|
|
|
|
include::modules/ztp-worker-node-node-selector-compatibility.adoc[leveloffset=+1]
|
|
|
|
:policy-gen-cr: PolicyGenerator
|
|
include::modules/ztp-worker-node-preparing-policies.adoc[leveloffset=+1]
|
|
|
|
:policy-gen-cr: PolicyGenTemplate
|
|
include::modules/ztp-worker-node-preparing-policies.adoc[leveloffset=+1]
|
|
|
|
include::modules/ztp-adding-worker-nodes.adoc[leveloffset=+1]
|
|
|
|
:!policy-gen-cr:
|