-
Bug
-
Resolution: Done
-
Critical
-
None
-
openshift-4.13
-
13
-
False
-
-
True
-
-
-
5
-
HCIDOCS 2024#13, HCIDOCS 2025#1
-
2
Task scope: Update Scaling user-provisioned cluster with information from IPI > Expanding the cluster. The missing section seems to be network configuration in the BareMetalHost.yaml.
Example YAML for static config from Preparing bm node:
---
apiVersion: v1
kind: Secret
metadata:
name: openshift-worker-<num>-network-config-secret
namespace: openshift-machine-api
type: Opaque
stringData:
nmstate: |
interfaces:
- name: <nic1_name>
type: ethernet
state: up
ipv4:
address:
- ip: <ip_address>
prefix-length: 24
enabled: true
dns-resolver:
config:
server:
- <dns_ip_address>
routes:
config:
- destination: 0.0.0.0/0
next-hop-address: <next_hop_ip_address>
next-hop-interface: <next_hop_nic1_name>
---
apiVersion: v1
kind: Secret
metadata:
name: openshift-worker-<num>-bmc-secret
namespace: openshift-machine-api
type: Opaque
data:
username: <base64_of_uid>
password: <base64_of_pwd>
---
apiVersion: metal3.io/v1alpha1
kind: BareMetalHost
metadata:
name: openshift-worker-<num>
namespace: openshift-machine-api
spec:
online: True
bootMACAddress: <nic1_mac_address>
bmc:
address: <protocol>://<bmc_url>
credentialsName: openshift-worker-<num>-bmc-secret
disableCertificateVerification: True
username: <bmc_username>
password: <bmc_password>
rootDeviceHints:
deviceName: <root_device_hint>
preprovisioningNetworkDataName: openshift-worker-<num>-network-config-secret
Note: There is also a BareMetalHost.yaml for DHCP, which should be included. It might be possible to use the same module (modules/ipi-install-preparing-the-bare-metal-node.adoc). If not, copy the YAMLs to a new module.
Current documentation (Scaling UPI cluster > Provisioning new hosts by using BMO):
---
# ...
---
apiVersion: metal3.io/v1alpha1
kind: BareMetalHost
metadata:
name: worker1
namespace: openshift-machine-api
spec:
bmc:
address: <protocol>://<bmc_url>
credentialsName: "worker1-bmc"
bootMACAddress: <nic1_mac_address>
externallyProvisioned: false
customDeploy:
method: install_coreos
online: true
userData:
name: worker-user-data-managed
namespace: openshift-machine-api
SME: Dmitry Tantsur
QE: Pedro Jose Amoedo Martinez
Description of problem:
Users following https://docs.openshift.com/container-platform/4.13/installing/installing_bare_metal/scaling-a-user-provisioned-cluster-with-the-bare-metal-operator.html#configuring-a-provisioning-resource-to-scale-user-provisioned-clusters_scaling-a-user-provisioned-cluster-with-the-bare-metal-operator don't know how to configure host networking
We keep pointing them to https://docs.openshift.com/container-platform/4.13/installing/installing_bare_metal_ipi/ipi-install-expanding-the-cluster.html because it's the same process, but the original workflow is for UPI clusters and this last doc is for IPI clusters.
We need to include in the "Scaling a user-provisioned cluster with the Bare Metal Operator" the instructions we have for configuring the host networking.
Version-Release number of selected component (if applicable):
openshift-4.13
- links to