mirror of
https://github.com/openshift/openshift-docs.git
synced 2026-02-05 12:46:18 +01:00
126 lines
4.7 KiB
Plaintext
126 lines
4.7 KiB
Plaintext
//Module included in the following assembly
|
|
//
|
|
//post_installation_configuration/cluster-tasks.adoc
|
|
|
|
:_mod-docs-content-type: PROCEDURE
|
|
[id="multi-architecture-modify-machine-set_{context}"]
|
|
= Adding a multi-architecture compute machine set to your Azure cluster
|
|
|
|
After creating a multi-architecture cluster, you can add nodes with different architectures.
|
|
|
|
You can add multi-architecture compute machines to a multi-architecture cluster in the following ways:
|
|
|
|
* Adding 64-bit x86 compute machines to a cluster that uses 64-bit ARM control plane machines and already includes 64-bit ARM compute machines. In this case, 64-bit x86 is considered the secondary architecture.
|
|
* Adding 64-bit ARM compute machines to a cluster that uses 64-bit x86 control plane machines and already includes 64-bit x86 compute machines. In this case, 64-bit ARM is considered the secondary architecture.
|
|
|
|
To create a custom compute machine set on Azure, see "Creating a compute machine set on Azure".
|
|
|
|
include::snippets/about-multiarch-tuning-operator.adoc[]
|
|
|
|
.Prerequisites
|
|
|
|
* You installed the OpenShift CLI (`oc`).
|
|
* You created a 64-bit ARM or 64-bit x86 boot image.
|
|
* You used the installation program to create a 64-bit ARM or 64-bit x86 single-architecture Azure cluster with the multi-architecture installer binary.
|
|
|
|
.Procedure
|
|
|
|
. Log in to the {oc-first}.
|
|
|
|
. Create a YAML file, and add the configuration to create a compute machine set to control the 64-bit ARM or 64-bit x86 compute nodes in your cluster.
|
|
+
|
|
.Example `MachineSet` object for an Azure 64-bit ARM or 64-bit x86 compute node
|
|
[source,yaml]
|
|
----
|
|
apiVersion: machine.openshift.io/v1beta1
|
|
kind: MachineSet
|
|
metadata:
|
|
labels:
|
|
machine.openshift.io/cluster-api-cluster: <infrastructure_id>
|
|
machine.openshift.io/cluster-api-machine-role: worker
|
|
machine.openshift.io/cluster-api-machine-type: worker
|
|
name: <infrastructure_id>-machine-set-0
|
|
namespace: openshift-machine-api
|
|
spec:
|
|
replicas: 2
|
|
selector:
|
|
matchLabels:
|
|
machine.openshift.io/cluster-api-cluster: <infrastructure_id>
|
|
machine.openshift.io/cluster-api-machineset: <infrastructure_id>-machine-set-0
|
|
template:
|
|
metadata:
|
|
labels:
|
|
machine.openshift.io/cluster-api-cluster: <infrastructure_id>
|
|
machine.openshift.io/cluster-api-machine-role: worker
|
|
machine.openshift.io/cluster-api-machine-type: worker
|
|
machine.openshift.io/cluster-api-machineset: <infrastructure_id>-machine-set-0
|
|
spec:
|
|
lifecycleHooks: {}
|
|
metadata: {}
|
|
providerSpec:
|
|
value:
|
|
acceleratedNetworking: true
|
|
apiVersion: machine.openshift.io/v1beta1
|
|
credentialsSecret:
|
|
name: azure-cloud-credentials
|
|
namespace: openshift-machine-api
|
|
image:
|
|
offer: ""
|
|
publisher: ""
|
|
resourceID: /resourceGroups/${RESOURCE_GROUP}/providers/Microsoft.Compute/galleries/${GALLERY_NAME}/images/rhcos-arm64/versions/1.0.0 <1>
|
|
sku: ""
|
|
version: ""
|
|
kind: AzureMachineProviderSpec
|
|
location: <region>
|
|
managedIdentity: <infrastructure_id>-identity
|
|
networkResourceGroup: <infrastructure_id>-rg
|
|
osDisk:
|
|
diskSettings: {}
|
|
diskSizeGB: 128
|
|
managedDisk:
|
|
storageAccountType: Premium_LRS
|
|
osType: Linux
|
|
publicIP: false
|
|
publicLoadBalancer: <infrastructure_id>
|
|
resourceGroup: <infrastructure_id>-rg
|
|
subnet: <infrastructure_id>-worker-subnet
|
|
userDataSecret:
|
|
name: worker-user-data
|
|
vmSize: Standard_D4ps_v5 <2>
|
|
vnet: <infrastructure_id>-vnet
|
|
zone: "<zone>"
|
|
----
|
|
<1> Set the `resourceID` parameter to either `arm64` or `amd64` boot image.
|
|
<2> Set the `vmSize` parameter to the instance type used in your installation. Some example instance types are `Standard_D4ps_v5` or `D8ps`.
|
|
|
|
. Create the compute machine set by running the following command:
|
|
+
|
|
[source,terminal]
|
|
----
|
|
$ oc create -f <file_name> <1>
|
|
----
|
|
<1> Replace `<file_name>` with the name of the YAML file with compute machine set configuration. For example: `arm64-machine-set-0.yaml`, or ``amd64-machine-set-0.yaml``.
|
|
|
|
.Verification
|
|
|
|
. Verify that the new machines are running by running the following command:
|
|
+
|
|
[source,terminal]
|
|
----
|
|
$ oc get machineset -n openshift-machine-api
|
|
----
|
|
+
|
|
The output must include the machine set that you created.
|
|
+
|
|
.Example output
|
|
[source,terminal]
|
|
----
|
|
NAME DESIRED CURRENT READY AVAILABLE AGE
|
|
<infrastructure_id>-machine-set-0 2 2 2 2 10m
|
|
----
|
|
. You can check if the nodes are ready and schedulable by running the following command:
|
|
+
|
|
[source,terminal]
|
|
----
|
|
$ oc get nodes
|
|
---- |