1
0
mirror of https://github.com/openshift/openshift-docs.git synced 2026-02-05 12:46:18 +01:00
Files
openshift-docs/modules/ibi-image-based-install-cluster-guide.adoc
2025-09-17 14:57:03 +00:00

42 lines
2.2 KiB
Plaintext

// Module included in the following assemblies:
// * edge_computing/image-based-install/ibi-understanding-image-based-install.adoc
:_mod-docs-content-type: CONCEPT
[id="ibi-image-based-install-cluster-guide_{context}"]
= Cluster guidelines for image-based installation and deployment
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".
* Create a seed image from a {sno} cluster that uses the same hardware as your target bare-metal host. The seed cluster must reflect your target cluster configuration for the following items:
** CPU topology
*** CPU architecture
*** Number of CPU cores
*** Tuned performance configuration, such as number of reserved CPUs
** IP version configuration, either IPv4, IPv6, or dual-stack networking
** Disconnected registry
+
[NOTE]
====
If the target cluster uses a disconnected registry, your seed cluster must use a disconnected registry. The registries do not have to be the same.
====
** FIPS configuration