Added explicit notes for Kiwi process first (suse-edge#677)

hardys · e-minguez · web-flow · commit 8633a64dfdd6 · 2025-06-09T16:49:42.000+02:00
Co-authored-by: e-minguez &lt;e.minguez@gmail.com&gt;
diff --git a/asciidoc/edge-book/releasenotes.adoc b/asciidoc/edge-book/releasenotes.adoc
@@ -59,6 +59,11 @@ Summary: SUSE Edge 3.3.0 is the first release in the SUSE Edge 3.3 release strea
 
 == Known Issues
 
+[WARNING]
+====
+If deploying new clusters, please follow <<guides-kiwi-builder-images>> to build fresh images first as this is now the first step required to create clusters for both {x86-64} and {aarch64} architectures as well as management and downstream clusters.
+====
+
 * When using `toolbox` in SUSE Linux Micro 6.1, the default container image does not contain some tools which were included in the previous 5.5 version.  The workaround is to configure toolbox to use the previous `suse/sle-micro/5.5/toolbox` container image, see `toolbox --help` for options to configure the image.
 * In some cases rolling upgrades via CAPI can result in Machines stuck in Deleting state, this will be resolved via a future update https://github.com/rancher/cluster-api-provider-rke2/issues/655[Upstream RKE2 provider issue 655]
 * In some cases when using a management cluster that has been upgraded from Edge 3.2, downstream rolling upgrades via CAPI can result in Machines stuck in Deleting state, this will be resolved via a future update https://github.com/rancher/cluster-api-provider-rke2/issues/661[Upstream RKE2 provider issue 661]
diff --git a/asciidoc/quickstart/eib.adoc b/asciidoc/quickstart/eib.adoc
@@ -25,7 +25,7 @@ Older versions, such as SUSE Linux Enterprise Micro 5.5, or 6.0 are not supporte
 
 * An {x86-64} physical host (or virtual machine) running SLES 15 SP6, openSUSE Leap 15.6, or openSUSE Tumbleweed.
 * An available container runtime (e.g. Podman)
-* A downloaded copy of the latest SUSE Linux Micro {version-sl-micro} SelfInstall ISO image found https://www.suse.com/download/sle-micro/[here].
+* A SUSE Linux Micro {version-sl-micro} SelfInstall ISO image created using the <<guides-kiwi-builder-images,Kiwi Builder procedure>>
 
 NOTE: Other operating systems may function so long as a compatible container runtime is available, but testing on other platforms has not been extensive. The documentation focuses on Podman, but the same functionality should be able to be achieved with Docker.
 
@@ -48,11 +48,11 @@ export CONFIG_DIR=$HOME/eib
 mkdir -p $CONFIG_DIR/base-images
 ----
 
-In the previous step we created a "base-images" directory that will host the SUSE Linux Micro {version-operatingsystem} input image, let's ensure that the downloaded image is copied over to the configuration directory:
+In the previous step we created a "base-images" directory that will host the SUSE Linux Micro {version-operatingsystem} input image, let's ensure that the image is copied over to the configuration directory:
 
 [,shell,subs="attributes"]
 ----
-cp /path/to/downloads/{micro-base-image-iso} $CONFIG_DIR/base-images/slemicro.iso
+cp /path/to/{micro-base-image-iso} $CONFIG_DIR/base-images/slemicro.iso
 ----
 
 
diff --git a/asciidoc/quickstart/elemental.adoc b/asciidoc/quickstart/elemental.adoc
@@ -219,19 +219,19 @@ This URL is used in the next step.
 
 == Build the image [[build-installation-media]]
 
-While the current version of Elemental has a way to build its own installation media, in SUSE Edge {version-edge} we do this with the Edge Image Builder instead, so the resulting system is built with https://www.suse.com/products/micro/[SUSE Linux Micro] as the base Operating System.
+While the current version of Elemental has a way to build its own installation media, in SUSE Edge {version-edge} we do this with Kiwi and Edge Image Builder instead, so the resulting system is built with https://www.suse.com/products/micro/[SUSE Linux Micro] as the base Operating System.
 
 [TIP]
 ====
-For more details on the Edge Image Builder, check out the <<quickstart-eib,Getting Started Guide for it>> and also the <<components-eib,Component Documentation>>.
+For more details on Kiwi, please follow <<guides-kiwi-builder-images,Kiwi Image Builder process>> to build fresh images first and for Edge Image Builder, check out the <<quickstart-eib,Edge Image Builder Getting Started Guide>> and also the <<components-eib,Component Documentation>>.
 ====
 
-From a Linux system with Podman installed, create the directories and place the base image:
+From a Linux system with Podman installed, create the directories and place the base image being built by Kiwi:
 
 [,bash]
 ----
 mkdir -p $ELEM/eib_quickstart/base-images
-cp /path/to/downloads/{micro-base-image-iso} $ELEM/eib_quickstart/base-images/
+cp /path/to/{micro-base-image-iso} $ELEM/eib_quickstart/base-images/
 mkdir -p $ELEM/eib_quickstart/elemental
 ----
 
diff --git a/asciidoc/quickstart/metal3.adoc b/asciidoc/quickstart/metal3.adoc
@@ -181,12 +181,14 @@ After some time, the controller pods should be running in the `capi-system`, `ca
 
 === Prepare downstream cluster image
 
-<<components-eib, Edge Image Builder>> is used to prepare a modified SLEMicro base image which is provisioned on downstream cluster hosts.
+<<guides-kiwi-builder-images, Kiwi>> and <<components-eib, Edge Image Builder>> are used to prepare a modified SLEMicro base image which is provisioned on downstream cluster hosts.
 
 In this guide, we cover the minimal configuration necessary to deploy the downstream cluster.
 
 ==== Image configuration
 
+NOTE: Please follow <<guides-kiwi-builder-images>> first to build a fresh image as the first step required to create clusters.
+
 When running Edge Image Builder, a directory is mounted from the host, so it is necessary to create a directory structure to store the configuration files used to define the target image.
 
 * `downstream-cluster-config.yaml` is the image definition file, see <<quickstart-eib>> for more details.
