Prerequisites for Bare Metal
Complete the common prerequisites first, then prepare the following for Bare Metal. ac does not create any machines. You provide the hosts yourself.
Host OS and Architecture
All hosts of the global cluster run the same host OS on the same host architecture. Choose the OS and the architecture before you push the OS images:
- Alauda OS M55, on
amd64only. - Alauda OS KU, on
amd64orarm64.
Use the hybrid Core Package if the host architecture differs from the architecture of the bootstrap node. See Download.
OS Images in the Registry
Download the OS archive for the host OS and architecture that you chose above, as described in Downloading Alauda OS. For a description of the archive, see Image Format by Provider.
The archive contains two OS images, the live ISO and the root filesystem. They come from the same archive but are not interchangeable. Push both images to the tkestack/ project of the external registry of global.registry, with the account of global.registry. The tkestack project must exist in the registry.
Fill in the form below with the ACP version, the host OS and architecture, the OS image tag (see Look Up the Image Tags), and the registry address. The form prints two sections: Push the OS images and Values for install-config.yaml.
Run the printed commands as root on the bootstrap node. The bootstrap node needs at least as much free space in /var/tmp as the size of the archive. The commands run the packtool of the Core Package as <extract-dir>/res/<arch>/packtool, in the same way that the other commands of the installation run ac.
An OS image tag is the file name of its OS archive without .tar, and the tag of both images of the archive.
Push the OS images
Values for install-config.yaml
Do not push with docker push or any other tool that rewrites the image manifest. The Alauda OS KU installer reads the manifest exactly as it is in the archive.
Continue when each tags/list response contains the tag. Otherwise, check the registry address, the credentials, the tkestack project, and the push output.
Keep the Values for install-config.yaml section. You paste these values into install-config.yaml in Create the global Cluster on Bare Metal.
Look Up the Image Tags
The two images have the same tag: the archive file name without .tar, such as alaudaos-44.m55.202610030151-0.x86_64. This tag is the value of both isoImageTag and rootImageTag.
To look up the tags in the registry later, run the following commands on a host that can reach the registry, such as the bootstrap node. If the registry needs no credentials, omit the read line and the -u option.
The output lists the tags of each repository, here for Alauda OS M55:
- The tag of
tkestack/baremetal-base-image-iso(tkestack/kubeos-isofor Alauda OS KU) is the ISO image tag. - The tag of
tkestack/baremetal-base-image(tkestack/kubeos-rootfsfor Alauda OS KU) is the root filesystem image tag.
If a repository lists more than one tag, use the tag of the archive that you downloaded for this ACP release and the host architecture. This can happen, for example, when images of another release or architecture were pushed earlier.
Hosts
Provide one host for each node of the global cluster. The number of hosts is controlPlane.replicas plus the replicas of every node group in computes. For example, 3 control plane nodes and 3 worker nodes need 6 hosts.
Each host later boots the installation ISO, which the first run of create builds in Build the Installation ISO. Prepare every host before it boots that ISO, as described in Prepare the Hosts:
- Wipe the OS install disk and any old boot disk, so that the host does not start an old OS. See Disks and Boot Order.
- Put the virtual CD or ISO first in the boot order.
- Set the clock in the BIOS/UEFI setup or through the BMC. All hosts use the same time zone, and their clocks differ by at most 10 seconds. See Clock.
- If the network gives the hosts no DHCP address, make sure that you can open the host console to configure an address. See Network in the Live ISO.
- On
arm64hosts, make sure that SMBIOS data is available. Anarm64host without SMBIOS cannot register. See arm64 Hosts.
Network
- An address during the live ISO boot, from DHCP or configured on the host console as described in Network in the Live ISO.
- A route from the hosts to the bootstrap node address, which is the IPv4 address that the hosts use to reach the bootstrap node. The hosts register through this address, on port
12443. Until the handover from the bootstrap cluster to theglobalcluster, the agents on the hosts also read their plans through it. The ISO download URL is on the same address and port, so the machine that you download the ISO with also needs a route to it. For the flows from the hosts to the bootstrap node, see Installation. - A control plane endpoint, as planned in Plan the Control Plane Endpoint. It is either a Self-built VIP with its VRID, or an external load balancer. The load balancer must forward every port marked Yes under Forward on load balancer in Platform Access Address and
globalVIP. You add the control plane hosts as its backends in Install the Cluster, before the second run ofcreate. If the hosts get their addresses from DHCP, you know them only after the hosts register.
Next Steps
In addition to the common values, you now have:
- The host OS and architecture.
- The values for
install-config.yamlthat the form printed: the ISO image tag and the root filesystem image tag. - The bootstrap node address.
Continue with Create the global Cluster on Bare Metal.