installing-restricted-networks-ibm-z.adoc

_attributes/common-attributes.adoc

Installing a cluster with z/VM on {ibm-z-title} and {ibm-linuxone-title} in a disconnected environment

In {product-title} version {product-version}, you can install a cluster on {ibm-z-name} or {ibm-linuxone-name} infrastructure that you provision in a disconnected environment.

Note	While this document refers to only {ibm-z-name}, all information in it also applies to {ibm-linuxone-name}.

Prerequisites

• You have completed the tasks in Preparing to install a cluster on {ibm-z-title} using user-provisioned infrastructure.

• You reviewed details about the {product-title} installation and update processes.

• You read the documentation on selecting a cluster installation method and preparing it for users.

• You mirrored the images for a disconnected installation to your registry and obtained the imageContentSources data for your version of {product-title}.

• Before you begin the installation process, you must move or remove any existing installation files. This ensures that the required installation files are created and updated during the installation process.

  Important

  Ensure that installation steps are done from a machine with access to the installation media.

• You provisioned persistent storage using {rh-storage} or other supported storage protocols for your cluster. To deploy a private image registry, you must set up persistent storage with ReadWriteMany access.

• If you use a firewall and plan to use the Telemetry service, you configured the firewall to allow the sites that your cluster requires access to.

  Note	Be sure to also review this site list if you are configuring a proxy.

modules/installation-about-restricted-network.adoc

modules/installation-infrastructure-user-infra.adoc

modules/installation-initializing-manual.adoc

Additional resources

• Installation configuration parameters for {ibm-z-name}

modules/installation-bare-metal-config-yaml.adoc

modules/installation-configure-proxy.adoc

modules/installation-three-node-cluster.adoc

modules/nw-operator-cr.adoc

modules/installation-user-infra-generate-k8s-manifest-ignition.adoc

modules/ibm-z-configure-nbde-with-static-ip.adoc

Additional resources

• Creating machine configs with Butane

modules/installation-ibm-z-user-infra-machines-iso.adoc

modules/installation-user-infra-machines-static-network.adoc

modules/installation-installing-bare-metal.adoc

modules/cli-logging-in-kubeadmin.adoc

modules/installation-approve-csrs.adoc

modules/installation-operators-config.adoc

modules/olm-restricted-networks-configuring-operatorhub.adoc

modules/installation-registry-storage-config.adoc

modules/registry-configuring-storage-baremetal.adoc

modules/installation-registry-storage-non-production.adoc

modules/installation-complete-user-infra.adoc

Additional resources

• How to generate SOSREPORT within {product-title} version 4 nodes without SSH

Next steps

• Customize your cluster.

• If the mirror registry that you used to install your cluster has a trusted CA, add it to the cluster by configuring additional trust stores.

• If necessary, you can opt out of remote health reporting.

• If necessary, see Registering your disconnected cluster