add support mixed archictecture (#841)

Author: alknopfler

asciidoc/product/atip-automated-provision.adoc

@@ -72,7 +72,6 @@ Much of the configuration via Edge Image Builder is possible, but in this guide,
 
 * A container runtime such as https://podman.io[Podman] or https://rancherdesktop.io[Rancher Desktop] is required to run Edge Image Builder.
 * The base image will be built using the following guide <<guides-kiwi-builder-images>> with the profile `Base-SelfInstall` (or `Base-RT-SelfInstall` for the Real-Time kernel). The process is the same for both architectures (x86-64 and aarch64).
-* To deploy aarch64 downstream clusters, you must set before the management cluster deployment the `deployArchitecture: arm64` parameter in the `metal3.yaml` file explained in <<arm64-mgmt-cluster,Management Cluster Documentation>>. This is required to ensure that the correct architecture is used for the downstream cluster.
 
 [NOTE]
 ====
@@ -342,7 +341,6 @@ Much of the configuration is possible with Edge Image Builder, but in this guide
 
 * A container runtime such as https://podman.io[Podman] or https://rancherdesktop.io[Rancher Desktop] is required to run Edge Image Builder.
 * The base image will be built using the following guide <<guides-kiwi-builder-images>> with the profile `Base-SelfInstall` (or `Base-RT-SelfInstall` for the Real-Time kernel). The process is the same for both architectures (x86-64 and aarch64).
-* To deploy aarch64 downstream clusters, you must set before the management cluster deployment the `deployArchitecture: arm64` parameter in the `metal3.yaml` file explained in <<arm64-mgmt-cluster,Management Cluster Documentation>>. This is required to ensure that the correct architecture is used for the downstream cluster.
 * If you want to use SR-IOV or any other workload which require a container image, a local private registry must be deployed and already configured (with/without TLS and/or authentication). This registry will be used to store the images and the helm chart OCI images.
 
 [NOTE]
@@ -639,6 +637,7 @@ metadata:
   labels:
     cluster-role: control-plane
 spec:
+  architecture: x86_64
   online: true
   bootMACAddress: ${BMC_MAC}
   rootDeviceHints:
@@ -657,7 +656,8 @@ where:
 
 [NOTE]
 ====
-If no network configuration for the host has been specified, either at image build time or through the `BareMetalHost` definition, an autoconfiguration mechanism (DHCP, DHCPv6, SLAAC) will be used. For more details or complex configurations, check the xref:advanced-network-configuration[].
+* Architecture must be either `x86_64` or `aarch64`, depending on the architecture of the bare-metal host to be enrolled.
+* If no network configuration for the host has been specified, either at image build time or through the `BareMetalHost` definition, an autoconfiguration mechanism (DHCP, DHCPv6, SLAAC) will be used. For more details or complex configurations, check the xref:advanced-network-configuration[].
 ====
 
 Once the file is created, the following command has to be executed in the management cluster to start enrolling the new bare-metal host in the management cluster:
@@ -953,6 +953,7 @@ metadata:
   labels:
     cluster-role: control-plane
 spec:
+  architecture: x86_64
   online: true
   bootMACAddress: ${BMC_NODE1_MAC}
   bmc:
@@ -972,6 +973,7 @@ Where:
 ====
 * If no network configuration for the host has been specified, either at image build time or through the `BareMetalHost` definition, an autoconfiguration mechanism (DHCP, DHCPv6, SLAAC) will be used. For more details or complex configurations, check the xref:advanced-network-configuration[].
 * Multi-node dual-stack or IPv6 only clusters are not yet supported.
+* Architecture must be either `x86_64` or `aarch64`, depending on the architecture of the bare-metal host to be enrolled.
 ====
 
 Once the file is created, the following command must be executed in the management cluster to start enrolling the bare-metal hosts in the management cluster:
@@ -1555,6 +1557,7 @@ metadata:
   labels:
     cluster-role: control-plane
 spec:
+  architecture: x86_64
   online: true
   bootMACAddress: ${BMC_MAC}
   rootDeviceHints:
@@ -1570,6 +1573,7 @@ spec:
 ====
 * If you need to deploy a multi-node cluster, the same process must be done for each node.
 * The `Metal3DataTemplate`, `networkData` and `Metal3 IPAM` are currently not supported; only the configuration via static secrets is fully supported.
+* Architecture must be either `x86_64` or `aarch64`, depending on the architecture of the bare-metal host to be enrolled.
 ====
 
 [#add-telco]

asciidoc/product/atip-management-cluster.adoc

@@ -878,29 +878,6 @@ metal3-ironic:
       size: "5Gi"
 
 ----
-[#arm64-mgmt-cluster]
-In case you want to deploy arm64 downstream clusters using this x86_64 management cluster, you need to add the following `deployArchitecture: arm64` to the `global` section of the `metal3.yaml` file:
-+
-[,yaml]
-----
-global:
-  ironicIP: ${METAL3_VIP}
-  enable_vmedia_tls: false
-  additionalTrustedCAs: false
-  deployArchitecture: arm64
-metal3-ironic:
-  global:
-    predictableNicNames: "true"
-  persistence:
-    ironic:
-      size: "5Gi"
-----
-
-[NOTE]
-====
-In the current version, a limitation exists regarding the use of `deployArchitecture: arm64`. Specifically, if you enable the deployment of downstream arm64 clusters using this directive, the management cluster will subsequently only be able to deploy this architecture.
-To deploy clusters on both architectures (x86_64 and arm64), you will need to provision two separate management clusters. This limitation will be removed in a future version.
-====
 
 [#metal3-media-server]
 [NOTE]

asciidoc/quickstart/metal3.adoc

@@ -353,6 +353,7 @@ metadata:
   labels:
     cluster-role: control-plane
 spec:
+  architecture: x86_64
   online: true
   bootMACAddress: "00:f3:65:8a:a3:b0"
   bmc: