6.6.6. 将节点、裸机主机和机器连接在一起
通过创建机器,然后将其链接到新的 BareMetalHost 对象和节点,继续创建新的 control plane 节点。
流程
运行以下命令,获取 control plane 节点的
providerID:$ oc get -n openshift-machine-api baremetalhost -l installer.openshift.io/role=control-plane -ojson | jq -r '.items[] | "baremetalhost:///openshift-machine-api/" + .metadata.name + "/" + .metadata.uid'输出示例
baremetalhost:///openshift-machine-api/master-00/6214c5cf-c798-4168-8c78-1ff1a3cd2cb4 baremetalhost:///openshift-machine-api/master-01/58fb60bd-b2a6-4ff3-a88d-208c33abf954 baremetalhost:///openshift-machine-api/master-02/dc5a94f3-625b-43f6-ab5a-7cc4fc79f105运行以下命令,获取标签的集群信息:
$ oc get machine -n openshift-machine-api \ -l machine.openshift.io/cluster-api-machine-role=master \ -L machine.openshift.io/cluster-api-cluster输出示例
NAME PHASE TYPE REGION ZONE AGE CLUSTER-API-CLUSTER ci-op-jcp3s7wx-ng5sd-master-0 Running 10h ci-op-jcp3s7wx-ng5sd ci-op-jcp3s7wx-ng5sd-master-1 Running 10h ci-op-jcp3s7wx-ng5sd ci-op-jcp3s7wx-ng5sd-master-2 Running 10h ci-op-jcp3s7wx-ng5sd通过创建一个类似如下的 yaml 文件,为新 control plane 节点创建
Machine对象:apiVersion: machine.openshift.io/v1beta1 kind: Machine metadata: annotations: metal3.io/BareMetalHost: openshift-machine-api/<new_control_plane_machine>1 finalizers: - machine.machine.openshift.io labels: machine.openshift.io/cluster-api-cluster: <cluster_api_cluster>2 machine.openshift.io/cluster-api-machine-role: master machine.openshift.io/cluster-api-machine-type: master name: <new_control_plane_machine>3 namespace: openshift-machine-api spec: metadata: {} providerID: <provider_id>4 providerSpec: value: apiVersion: baremetal.cluster.k8s.io/v1alpha1 hostSelector: {} image: checksum: "" url: "" kind: BareMetalMachineProviderSpec userData: name: master-user-data-managed其中:
<new_control_plane_machine>- 指定新机器的名称,可以与之前删除的机器名称相同。
<cluster_api_cluster>-
为其他 control plane 机器指定
CLUSTER-API-CLUSTER值,如上一步的输出中所示。 <provider_id>-
指定新裸机主机的
providerID值,如前一步的输出中所示。
应该会发出以下警告:
Warning: metadata.finalizers: "machine.machine.openshift.io": prefer a domain-qualified finalizer name to avoid accidental conflicts with other finalizer writers通过在单个 bash shell 会话中执行以下步骤,将新的 control plane 节点和
Machine对象链接到BareMetalHost对象:运行以下命令来定义
NEW_NODE_NAME变量:$ NEW_NODE_NAME=<new_node_name>将
<new_node_name>替换为新 control plane 节点的名称。运行以下命令定义
NEW_MACHINE_NAME变量:$ NEW_MACHINE_NAME=<new_machine_name>将
<new_machine_name>替换为新机器的名称。运行以下命令来定义
BMH_UID,使其从新节点的BareMetalHost对象中提取:$ BMH_UID=$(oc get -n openshift-machine-api bmh $NEW_NODE_NAME -ojson | jq -r .metadata.uid)$ echo $BMH_UID运行以下命令,将
consumerRef对象修补到裸机主机中:$ oc patch -n openshift-machine-api bmh $NEW_NODE_NAME --type merge --patch '{"spec":{"consumerRef":{"apiVersion":"machine.openshift.io/v1beta1","kind":"Machine","name":"'$NEW_MACHINE_NAME'","namespace":"openshift-machine-api"}}}'运行以下命令,将
providerID值修补到新节点:$ oc patch node $NEW_NODE_NAME --type merge --patch '{"spec":{"providerID":"baremetalhost:///openshift-machine-api/'$NEW_NODE_NAME'/'$BMH_UID'"}}'运行以下命令,查看
providerID值:$ oc get node -l node-role.kubernetes.io/control-plane -ojson | jq -r '.items[] | .metadata.name + " " + .spec.providerID'
运行以下命令,将
BareMetalHost对象的poweredOn状态设置为true:$ oc patch -n openshift-machine-api bmh $NEW_NODE_NAME --subresource status --type json -p '[{"op":"replace","path":"/status/poweredOn","value":true}]'运行以下命令,查看
BareMetalHost对象的poweredOn状态:$ oc get bmh -n openshift-machine-api -ojson | jq -r '.items[] | .metadata.name + " PoweredOn:" + (.status.poweredOn | tostring)'运行以下命令,查看
BareMetalHost对象的置备状态:$ oc get bmh -n openshift-machine-api -ojson | jq -r '.items[] | .metadata.name + " ProvisioningState:" + .status.provisioning.state'重要如果置备状态不是
unmanaged,请运行以下命令来更改置备状态:$ oc patch -n openshift-machine-api bmh $NEW_NODE_NAME --subresource status --type json -p '[{"op":"replace","path":"/status/provisioning/state","value":"unmanaged"}]'运行以下命令,将机器的状态设置为
Provisioned:$ oc patch -n openshift-machine-api machines $NEW_MACHINE_NAME -n openshift-machine-api --subresource status --type json -p '[{"op":"replace","path":"/status/phase","value":"Provisioned"}]'