From 42748c554fc8d2e1ba2e764388b8f558f4891723 Mon Sep 17 00:00:00 2001 From: Ronan Hennessy Date: Thu, 8 May 2025 11:44:05 +0100 Subject: [PATCH] TELCODOCS-2300: Clarifying network config limitations for IBI --- modules/ibi-create-standalone-config-iso.adoc | 8 +------- modules/ibi-image-based-install-cluster-guide.adoc | 4 ++++ 2 files changed, 5 insertions(+), 7 deletions(-) diff --git a/modules/ibi-create-standalone-config-iso.adoc b/modules/ibi-create-standalone-config-iso.adoc index b49f3905a4..ccb43c4490 100644 --- a/modules/ibi-create-standalone-config-iso.adoc +++ b/modules/ibi-create-standalone-config-iso.adoc @@ -57,14 +57,8 @@ controlPlane: name: master replicas: 1 networking: - clusterNetwork: - - cidr: 10.128.0.0/14 - hostPrefix: 23 machineNetwork: - cidr: 192.168.200.0/24 - networkType: OVNKubernetes - serviceNetwork: - - 172.30.0.0/16 platform: none: {} fips: false @@ -78,7 +72,7 @@ sshKey: 'ssh-rsa ' If your cluster deployment requires a proxy configuration, you must do the following: * Create a seed image from a seed cluster featuring a proxy configuration. The proxy configurations do not have to match. -* Configure the machineNetwork field in your installation manifest. +* Configure the `machineNetwork` field in your installation manifest. ==== -- diff --git a/modules/ibi-image-based-install-cluster-guide.adoc b/modules/ibi-image-based-install-cluster-guide.adoc index 593fe4a0e3..d039a4bab6 100644 --- a/modules/ibi-image-based-install-cluster-guide.adoc +++ b/modules/ibi-image-based-install-cluster-guide.adoc @@ -7,14 +7,18 @@ For a successful image-based installation and deployment, see the following guidelines. +[id="ibi-cluster-guidelines_{context}"] == Cluster guidelines * If you are using {rh-rhacm-first}, to avoid including any {rh-rhacm} resources in your seed image, you need to disable all optional {rh-rhacm} add-ons before generating the seed image. +[id="ibi-seed-cluster-guidelines_{context}"] == Seed cluster guidelines * If your cluster deployment at the edge of the network requires a proxy configuration, you must create a seed image from a seed cluster featuring a proxy configuration. The proxy configurations do not have to match. +* The `clusterNetwork` and `serviceNetwork` network configurations in the seed cluster persist to the deployed cluster. The Lifecycle Agent embeds these settings in the seed image. You cannot change these settings later in the image-based installation and deployment process. + * If you set a maximum transmission unit (MTU) in the seed cluster, you must set the same MTU value in the static network configuration for the image-based configuration ISO. * Your {sno} seed cluster must have a shared `/var/lib/containers` directory for precaching images during an image-based installation. For more information see "Configuring a shared container partition between ostree stateroots".