Skip to content

Commit 5b6e937

Browse files
committed
atip-management-cluster: clarify EIB introduction
Fixes: #438
1 parent b473280 commit 5b6e937

File tree

1 file changed

+3
-2
lines changed

1 file changed

+3
-2
lines changed

asciidoc/product/atip-management-cluster.adoc

Lines changed: 3 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -76,8 +76,9 @@ For more information about Edge Image Builder, see <<components-eib,Edge Image B
7676
[#mgmt-cluster-image-preparation-connected]
7777
=== Image preparation for connected environments
7878

79-
Using Edge Image Builder to create the image for the management cluster, a lot of configurations can be customized, but in this document, we cover the minimal configurations necessary to set up the management cluster.
80-
Edge Image Builder is typically run from inside a container so, if you do not already have a way to run containers, we need to start by installing a container runtime such as https://podman.io[Podman] or https://rancherdesktop.io[Rancher Desktop]. For this guide, we assume you already have a container runtime available.
79+
Edge Image Builder is used to create the image for the management cluster, in this document we cover the minimal configuration necessary to set up the management cluster.
80+
81+
Edge Image Builder runs inside a container, so a container runtime is required such as https://podman.io[Podman] or https://rancherdesktop.io[Rancher Desktop]. For this guide, we assume podman is available.
8182

8283
Also, as a prerequisite to deploy a highly available management cluster, you need to reserve three IPs in your network:
8384
- `apiVIP` for the API VIP Address (used to access the Kubernetes API server).

0 commit comments

Comments
 (0)