mirror of
https://github.com/openshift/openshift-docs.git
synced 2026-02-05 21:46:22 +01:00
107 lines
3.7 KiB
Plaintext
107 lines
3.7 KiB
Plaintext
//Module included in the following assembly
|
|
//
|
|
//post_installation_configuration/cluster-tasks.adoc
|
|
|
|
:_content-type: PROCEDURE
|
|
[id="multi-architecture-modify-machine-set_{context}"]
|
|
|
|
= Adding a compute machine set to your cluster using the `arm64` boot image
|
|
|
|
To add `arm64` worker nodes to your multi-architecture cluster, you must create an Azure compute machine set that uses the `arm64` boot image. To create your own custom compute machine set on Azure, see "Creating a compute machine set on Azure".
|
|
|
|
.Prerequisites
|
|
|
|
* You installed the OpenShift CLI (`oc`).
|
|
|
|
.Procedure
|
|
* Create a compute machine set and modify the `resourceID` and `vmSize` parameters with the following command. This compute machine set will control the `arm64` worker nodes in your cluster:
|
|
+
|
|
[source,terminal]
|
|
----
|
|
$ oc create -f arm64-machine-set-0.yaml
|
|
----
|
|
.Sample YAML compute machine set with `arm64` boot image
|
|
+
|
|
[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>-arm64-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>-arm64-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>-arm64-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 the `arm64` 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`.
|
|
|
|
.Verification
|
|
. Verify that the new ARM64 machines are running by entering the following command:
|
|
+
|
|
[source,terminal]
|
|
----
|
|
$ oc get machineset -n openshift-machine-api
|
|
----
|
|
+
|
|
.Example output
|
|
[source,terminal]
|
|
----
|
|
NAME DESIRED CURRENT READY AVAILABLE AGE
|
|
<infrastructure_id>-arm64-machine-set-0 2 2 2 2 10m
|
|
----
|
|
. You can check that the nodes are ready and scheduable with the following command:
|
|
+
|
|
[source, terminal]
|
|
----
|
|
$ oc get nodes
|
|
---- |