Skip to content

OSDOCS-19785 Bare Metal Multi Arch Support - iPXE/Network boot#111611

Open
bscott-rh wants to merge 2 commits into
openshift:mainfrom
bscott-rh:OSDOCS-19785
Open

OSDOCS-19785 Bare Metal Multi Arch Support - iPXE/Network boot#111611
bscott-rh wants to merge 2 commits into
openshift:mainfrom
bscott-rh:OSDOCS-19785

Conversation

@bscott-rh
Copy link
Copy Markdown
Contributor

@bscott-rh bscott-rh commented May 13, 2026

Version(s):
4.22

Issue:
https://redhat.atlassian.net/browse/OSDOCS-19785

Link to docs preview:
Preparing the bare metal node
BareMetalHost spec

QE review:

  • QE has approved this change.

@bscott-rh bscott-rh added this to the Planned for 4.22 GA milestone May 13, 2026
@openshift-ci openshift-ci Bot added the size/M Denotes a PR that changes 30-99 lines, ignoring generated files. label May 13, 2026
@ocpdocs-previewbot
Copy link
Copy Markdown

ocpdocs-previewbot commented May 13, 2026

Comment thread modules/ipi-install-preparing-the-bare-metal-node.adoc
|Parameters |Description

| `architecture`
| Specifies the CPU architecture of the underlying machine. Supported values are `aarch64` and `x86_64`. If this value is not specified, it will default to the architecture of the control plane.
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@honza I believe our support here is currently limited to adding ARM workers to an x86 control plane (not the other way around)?
We might want to make that explicit.

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

That's correct.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks, updated this

* You have installed a bare-metal cluster.
* If you intend to use DHCP to provide the new machine's IP address, you have a DHCP server on your network.
* If you intend to use PXE to provide the boot image, you have a PXE server on your network.
* If you intend to install a machine of a different architecture than the control plane, you installed the cluster with the multi-architecture release image.
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm assuming you can upgrade into (or out of) a multiarch payload as well. I'm not actually sure how that would work with OSUS, you might have to bypass that and enter a specific release image digest.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Updated this prerequisite to be more broad, and added a link to the docs on how to migrate a live cluster to the multi arch image.

@openshift-ci
Copy link
Copy Markdown

openshift-ci Bot commented May 14, 2026

@bscott-rh: all tests passed!

Full PR test history. Your PR dashboard.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

@bscott-rh
Copy link
Copy Markdown
Contributor Author

@honza can you please provide QE review for this PR? I will also tag you in the release note. Thank you

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

branch/enterprise-4.22 size/M Denotes a PR that changes 30-99 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants